| 1 |
@issue |
| 2 |
Feature: Issue #462-- Invalid JSON output when --include option selects no features |
| 3 |
|
| 4 |
. Invalid JSON output is generated when no features are selected in a test-run. |
| 5 |
. For example, this may be the case when the --include option is used. |
| 6 |
|
| 7 |
|
| 8 |
Background: |
| 9 |
Given a new working directory |
| 10 |
And a file named "features/steps/pass_steps.py" with: |
| 11 |
""" |
| 12 |
from behave import step |
| 13 |
|
| 14 |
@step('{word:w} step passes') |
| 15 |
def step_passes(context, word): |
| 16 |
pass |
| 17 |
""" |
| 18 |
And a file named "features/passing.feature" with: |
| 19 |
""" |
| 20 |
Feature: |
| 21 |
Scenario: |
| 22 |
Given a step passes |
| 23 |
""" |
| 24 |
|
| 25 |
|
| 26 |
Scenario: Include Option selects no feature files |
| 27 |
When I run "behave -f json -i __unknown__.feature" |
| 28 |
Then it should pass with: |
| 29 |
""" |
| 30 |
0 features passed, 0 failed, 0 skipped |
| 31 |
0 scenarios passed, 0 failed, 0 skipped |
| 32 |
""" |
| 33 |
And the command output should contain: |
| 34 |
""" |
| 35 |
[ |
| 36 |
] |
| 37 |
""" |
| 38 |
|