1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
|
@issue
Feature: Issue #42 Nice to have snippets for all unimplemented steps taking into account of the tags fltering
As a user
I want that all undefined steps are reported,
not only just the first one in a scenario.
In addition, all known steps after the first undefined step in a scenario
should be marked as skipped (even failing ones).
Background: Test Setup
Given a new working directory
And a file named "features/steps/steps.py" with:
"""
from behave import given, when, then
@given(u'I enter a "{name}"')
def step(context, name):
context.name = name
@when(u'I enter a "{name}"')
def step(context, name):
context.name = name
@then(u'the name is "{name}"')
def step(context, name):
assert context.name == name
"""
Scenario: One undefined step in a scenario
Given a file named "features/issue42_missing1.feature" with:
"""
Feature: Missing Given-Step in a Scenario
Scenario:
Given an unknown step
When I enter a "Alice"
Then the name is "Alice"
"""
When I run "behave -f plain features/issue42_missing1.feature"
Then it should fail with:
"""
0 steps passed, 0 failed, 2 skipped, 1 undefined
"""
And the command output should contain:
"""
You can implement step definitions for undefined steps with these snippets:
@given(u'an unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: Given an unknown step')
"""
Scenario: Two undefined steps in a scenario
Given a file named "features/issue42_missing2.feature" with:
"""
Feature: Missing Given and When steps in a Scenario
Scenario:
Given an unknown step
When another unknown step
And I enter a "Alice"
Then the name is "Alice"
"""
When I run "behave -f plain features/issue42_missing2.feature"
Then it should fail with:
"""
0 steps passed, 0 failed, 2 skipped, 2 undefined
"""
And the command output should contain:
"""
You can implement step definitions for undefined steps with these snippets:
@given(u'an unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: Given an unknown step')
@when(u'another unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: When another unknown step')
"""
Scenario: Two undefined steps in the middle with passing steps
Given a file named "features/issue42_missing3.feature" with:
"""
Feature: Missing 2 When steps after passing step
Scenario:
When I enter a "Alice"
And an unknown step
And another unknown step
Then the name is "Alice"
"""
When I run "behave -f plain features/issue42_missing3.feature"
Then it should fail with:
"""
1 step passed, 0 failed, 1 skipped, 2 undefined
"""
And the command output should contain:
"""
You can implement step definitions for undefined steps with these snippets:
@when(u'an unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: When an unknown step')
@when(u'another unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: When another unknown step')
"""
Scenario: Undefined steps are detected if they occur after a failing step
Given a file named "features/issue42_missing4.feature" with:
"""
Feature: Missing 2 When steps after passing step
Scenario:
When I enter a "Alice"
Then the name is "Bob"
And an unknown step
And another unknown step
"""
When I run "behave -f plain features/issue42_missing4.feature"
Then it should fail with:
"""
1 step passed, 1 failed, 0 skipped, 2 undefined
"""
And the command output should contain:
"""
You can implement step definitions for undefined steps with these snippets:
@then(u'an unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: Then an unknown step')
@then(u'another unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: Then another unknown step')
"""
Scenario: Failing step after first undefined step should be marked as skipped
Given a file named "features/issue42_missing4.feature" with:
"""
Feature: Missing 2 When steps after passing step
Scenario:
When I enter a "Alice"
And an unknown step
Then the name is "Bob"
And another unknown step
"""
When I run "behave -f plain features/issue42_missing4.feature"
Then it should fail with:
"""
1 step passed, 0 failed, 1 skipped, 2 undefined
"""
And the command output should contain:
"""
You can implement step definitions for undefined steps with these snippets:
@when(u'an unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: When an unknown step')
@then(u'another unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: Then another unknown step')
"""
Scenario: Two undefined steps in scenario outline
Given a file named "features/issue42_missing5.feature" with:
"""
Feature: Missing Given and When Step in a Scenario Outline
Scenario Outline:
Given an unknown step
When another unknown step
And I enter a "<name>"
Then the name is "<name>"
Examples:
|name |
|Alice|
|Bob |
"""
When I run "behave -f plain features/issue42_missing5.feature"
Then it should fail with:
"""
0 steps passed, 0 failed, 4 skipped, 4 undefined
"""
And the command output should contain:
"""
You can implement step definitions for undefined steps with these snippets:
@given(u'an unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: Given an unknown step')
@when(u'another unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: When another unknown step')
"""
Scenario: Two undefined steps and run with tags
Given a file named "features/issue42_missing6.feature" with:
"""
Feature: Missing steps in tagged scenarios
@tag1
Scenario:
When I enter a "Alice"
And an unknown step
Then the name is "Bob"
@tag1
Scenario:
When I enter a "Alice"
And another unknown step
Then the name is "Bob"
@another_tag
Scenario:
When I enter a "Alice"
And yet another unknown step
Then the name is "Bob"
"""
When I run "behave -f plain --tags tag1 features/issue42_missing6.feature"
Then it should fail with:
"""
2 steps passed, 0 failed, 5 skipped, 2 undefined
"""
And the command output should contain:
"""
You can implement step definitions for undefined steps with these snippets:
@when(u'an unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: When an unknown step')
@when(u'another unknown step')
def step_impl(context):
raise NotImplementedError(u'STEP: When another unknown step')
"""
|
