| 1 |
Feature: Summary with Undefined Steps |
| 2 |
|
| 3 |
. SPECIFICATION: |
| 4 |
. * An undefined step should be counted as "undefined" step. |
| 5 |
. * An undefined step should cause its scenario to fail. |
| 6 |
. * If an undefined step is detected the remaining scenario steps are skipped. |
| 7 |
. |
| 8 |
. RELATED TO: |
| 9 |
. * issue #42 Multiple undefined steps in same scenario are detected. |
| 10 |
|
| 11 |
|
| 12 |
@setup |
| 13 |
Scenario: Test Setup |
| 14 |
Given a new working directory |
| 15 |
And a file named "features/steps/passing_steps.py" with: |
| 16 |
""" |
| 17 |
from behave import step |
| 18 |
|
| 19 |
@step('a step passes') |
| 20 |
def step_passes(context): |
| 21 |
pass |
| 22 |
""" |
| 23 |
|
| 24 |
Scenario: Undefined step as first step in a scenario |
| 25 |
Given a file named "features/summary_undefined_first_step.feature" with: |
| 26 |
""" |
| 27 |
Feature: |
| 28 |
Scenario: |
| 29 |
Given an undefined step is used |
| 30 |
When a step passes |
| 31 |
Then a step passes |
| 32 |
""" |
| 33 |
When I run "behave -f plain features/summary_undefined_first_step.feature" |
| 34 |
Then it should fail with: |
| 35 |
""" |
| 36 |
0 features passed, 1 failed, 0 skipped |
| 37 |
0 scenarios passed, 1 failed, 0 skipped |
| 38 |
0 steps passed, 0 failed, 2 skipped, 1 undefined |
| 39 |
""" |
| 40 |
|
| 41 |
Scenario: Undefined step as last step in a scenario |
| 42 |
Given a file named "features/summary_undefined_last_step.feature" with: |
| 43 |
""" |
| 44 |
Feature: |
| 45 |
Scenario: |
| 46 |
Given a step passes |
| 47 |
When an undefined step is used |
| 48 |
""" |
| 49 |
When I run "behave -f plain features/summary_undefined_last_step.feature" |
| 50 |
Then it should fail with: |
| 51 |
""" |
| 52 |
0 features passed, 1 failed, 0 skipped |
| 53 |
0 scenarios passed, 1 failed, 0 skipped |
| 54 |
1 step passed, 0 failed, 0 skipped, 1 undefined |
| 55 |
""" |
| 56 |
|
| 57 |
|
| 58 |
Scenario: Undefined step as middle step in a scenario |
| 59 |
Given a file named "features/summary_undefined_middle_step.feature" with: |
| 60 |
""" |
| 61 |
Feature: |
| 62 |
Scenario: |
| 63 |
Given a step passes |
| 64 |
When an undefined step is used |
| 65 |
Then a step passes |
| 66 |
And a step passes |
| 67 |
""" |
| 68 |
When I run "behave -f plain features/summary_undefined_middle_step.feature" |
| 69 |
Then it should fail with: |
| 70 |
""" |
| 71 |
0 features passed, 1 failed, 0 skipped |
| 72 |
0 scenarios passed, 1 failed, 0 skipped |
| 73 |
1 step passed, 0 failed, 2 skipped, 1 undefined |
| 74 |
""" |
| 75 |
|
| 76 |
Scenario: Two undefined steps in same scenario, all are detected (skipped) |
| 77 |
Given a file named "features/summary_undefined_step2.feature" with: |
| 78 |
""" |
| 79 |
Feature: |
| 80 |
Scenario: |
| 81 |
Given a step passes |
| 82 |
When an undefined step is used |
| 83 |
Then a step passes |
| 84 |
And another undefined step is used |
| 85 |
""" |
| 86 |
When I run "behave -f plain features/summary_undefined_step2.feature" |
| 87 |
Then it should fail with: |
| 88 |
""" |
| 89 |
0 features passed, 1 failed, 0 skipped |
| 90 |
0 scenarios passed, 1 failed, 0 skipped |
| 91 |
1 step passed, 0 failed, 1 skipped, 2 undefined |
| 92 |
""" |
| 93 |
|
| 94 |
|
| 95 |
Scenario: Two undefined steps in different scenarios |
| 96 |
Given a file named "features/summary_undefined_step_and_another.feature" with: |
| 97 |
""" |
| 98 |
Feature: |
| 99 |
Scenario: |
| 100 |
Given a step passes |
| 101 |
When an undefined step is used |
| 102 |
Then a step passes |
| 103 |
|
| 104 |
Scenario: |
| 105 |
Given an undefined step is used |
| 106 |
When a step passes |
| 107 |
""" |
| 108 |
When I run "behave -f plain features/summary_undefined_step_and_another.feature" |
| 109 |
Then it should fail with: |
| 110 |
""" |
| 111 |
0 features passed, 1 failed, 0 skipped |
| 112 |
0 scenarios passed, 2 failed, 0 skipped |
| 113 |
1 step passed, 0 failed, 2 skipped, 2 undefined |
| 114 |
""" |