| 1 |
@slow |
| 2 |
Feature: Validate JSON Formatter Output |
| 3 |
|
| 4 |
As a tester |
| 5 |
I want that the JSON output is validated against its JSON schema |
| 6 |
So that the JSON formatter generates valid JSON output. |
| 7 |
|
| 8 |
| NOTES: |
| 9 |
| Some have the behave testruns may contain failures (@xfail). |
| 10 |
| This should lead to more realistic JSON output, too. |
| 11 |
|
| 12 |
Scenario: Validate JSON output from features/ test run |
| 13 |
Given I use the current directory as working directory |
| 14 |
When I run "behave -f json -o testrun1.json features/" |
| 15 |
When I run "bin/jsonschema_validate.py testrun1.json" |
| 16 |
Then it should pass with: |
| 17 |
""" |
| 18 |
validate: testrun1.json ... OK |
| 19 |
""" |
| 20 |
|
| 21 |
Scenario: Validate JSON output from issue.features/ test run |
| 22 |
Given I use the current directory as working directory |
| 23 |
When I run "behave -f json -o testrun2.json issue.features/" |
| 24 |
When I run "bin/jsonschema_validate.py testrun2.json" |
| 25 |
Then it should pass with: |
| 26 |
""" |
| 27 |
validate: testrun2.json ... OK |
| 28 |
""" |
| 29 |
|
| 30 |
Scenario: Validate JSON output from tools/test-features/ test run |
| 31 |
Given I use the current directory as working directory |
| 32 |
When I run "behave -f json -o testrun3.json tools/test-features/" |
| 33 |
When I run "bin/jsonschema_validate.py testrun3.json" |
| 34 |
Then it should pass with: |
| 35 |
""" |
| 36 |
validate: testrun3.json ... OK |
| 37 |
""" |