Debian Codegraph @

features/step.undefined_steps.feature

raw
1 Feature: Undefined Step
2
3 . TERMINOLOGY:
4 . * An undefined step is a step without matching step implementation.
5 .
6 . SPECIFICATION:
7 . * An undefined step should be reported after the run.
8 . * An undefined step should cause its scenario to fail.
9 . * If an undefined step is detected the remaining scenario steps are skipped.
10 . * All undefined steps in a scenario should be reported (issue #42).
11 . * Undefined steps should be detected even after a step fails in a scenario.
12 . * Each undefined step should be reported only once.
13 . * If a scenario is disabled (by tag expression, etc.),
14 . the undefined step discovery should not occur.
15 . This allows to prepare scenarios that are not intended to run (yet).
16 . * Option --dry-run should discover undefined steps, too.
17 .
18 . RELATED TO:
19 . * issue #42 Multiple undefined steps in same scenario are detected.
20
21
22 @setup
23 Scenario: Feature Setup
24 Given a new working directory
25 And a file named "features/steps/passing_steps.py" with:
26 """
27 from behave import step
28
29 @step('a step passes')
30 def step_passes(context):
31 pass
32
33 @step('a step fails')
34 def step_fails(context):
35 assert False, "XFAIL"
36 """
37 And a file named "features/undefined_last_step.feature" with:
38 """
39 Feature:
40 Scenario:
41 Given a step passes
42 When an undefined step is used
43 """
44
45 Scenario: An undefined step should be reported
46 When I run "behave -f plain -T features/undefined_last_step.feature"
47 Then it should fail
48 And the command output should contain:
49 """
50 Feature:
51 Scenario:
52 Given a step passes ... passed
53 When an undefined step is used ... undefined
54 """
55 And the command output should contain:
56 """
57 You can implement step definitions for undefined steps with these snippets:
58
59 @when(u'an undefined step is used')
60 def step_impl(context):
61 raise NotImplementedError(u'STEP: When an undefined step is used')
62 """
63 And an undefined-step snippet should exist for "When an undefined step is used"
64
65
66 Scenario: An undefined step should cause its scenario to fail
67 When I run "behave -f plain features/undefined_last_step.feature"
68 Then it should fail with:
69 """
70 0 features passed, 1 failed, 0 skipped
71 0 scenarios passed, 1 failed, 0 skipped
72 1 step passed, 0 failed, 0 skipped, 1 undefined
73 """
74
75
76 Scenario: Additional scenario steps after an undefined step are skipped
77 Given a file named "features/undefined_step_and_more.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 a step fails
85 """
86 When I run "behave -f plain -T features/undefined_step_and_more.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, 2 skipped, 1 undefined
92 """
93 And the command output should contain:
94 """
95 Feature:
96 Scenario:
97 Given a step passes ... passed
98 When an undefined step is used ... undefined
99 """
100
101
102 Scenario: Two undefined steps in same scenario should be detected
103 Given a file named "features/two_undefined_steps1.feature" with:
104 """
105 Feature:
106 Scenario:
107 Given a step passes
108 When an undefined step is used
109 And a step fails
110 Then another undefined step is used
111 """
112 When I run "behave -f plain -T features/two_undefined_steps1.feature"
113 Then it should fail with:
114 """
115 0 features passed, 1 failed, 0 skipped
116 0 scenarios passed, 1 failed, 0 skipped
117 1 step passed, 0 failed, 1 skipped, 2 undefined
118 """
119 And the command output should contain:
120 """
121 Feature:
122 Scenario:
123 Given a step passes ... passed
124 When an undefined step is used ... undefined
125 """
126 And undefined-step snippets should exist for:
127 | Step |
128 | When an undefined step is used |
129 | Then another undefined step is used |
130 But the command output should not contain:
131 """
132 And a step fails ... skipped
133 Then another undefined step is used ... undefined
134 """
135
136
137 Scenario: Two undefined steps in different scenarios
138 Given a file named "features/two_undefined_steps2.feature" with:
139 """
140 Feature:
141 Scenario:
142 Given a step passes
143 When an undefined step is used
144
145 Scenario:
146 Given another undefined step is used
147 When a step passes
148 """
149 When I run "behave -f plain -T features/two_undefined_steps2.feature"
150 Then it should fail with:
151 """
152 0 features passed, 1 failed, 0 skipped
153 0 scenarios passed, 2 failed, 0 skipped
154 1 step passed, 0 failed, 1 skipped, 2 undefined
155 """
156 And the command output should contain:
157 """
158 Feature:
159 Scenario:
160 Given a step passes ... passed
161 When an undefined step is used ... undefined
162
163 Scenario:
164 Given another undefined step is used ... undefined
165 """
166 And undefined-step snippets should exist for:
167 | Step |
168 | When an undefined step is used |
169 | Given another undefined step is used |
170
171
172 Scenario: Undefined step in Scenario Outline
173 Given a file named "features/undefined_step_in_scenario_outline.feature" with:
174 """
175 Feature:
176 Scenario Outline:
177 Given a step <outcome1>
178 When an undefined step is used
179 Then a step <outcome2>
180
181 Examples:
182 | outcome1 | outcome2 |
183 | passes | passes |
184 | passes | fails |
185 | fails | passes |
186 | fails | fails |
187 """
188 When I run "behave -f plain -T features/undefined_step_in_scenario_outline.feature"
189 Then it should fail with:
190 """
191 0 features passed, 1 failed, 0 skipped
192 0 scenarios passed, 4 failed, 0 skipped
193 2 steps passed, 2 failed, 4 skipped, 4 undefined
194 """
195 And an undefined-step snippet should exist for "When an undefined step is used"
196 And the command output should contain:
197 """
198 Feature:
199 Scenario Outline: -- @1.1
200 Given a step passes ... passed
201 When an undefined step is used ... undefined
202
203 Scenario Outline: -- @1.2
204 Given a step passes ... passed
205 When an undefined step is used ... undefined
206
207 Scenario Outline: -- @1.3
208 Given a step fails ... failed
209 Assertion Failed: XFAIL
210
211 Scenario Outline: -- @1.4
212 Given a step fails ... failed
213 Assertion Failed: XFAIL
214 """
215
216
217 Scenario: Two undefined step in Scenario Outline
218 Given a file named "features/two_undefined_step_in_scenario_outline.feature" with:
219 """
220 Feature:
221 Scenario Outline:
222 Given a step <outcome1>
223 When an undefined step is used
224 Then a step <outcome2>
225 And another undefined step is used
226
227 Examples:
228 | outcome1 | outcome2 |
229 | passes | passes |
230 | passes | fails |
231 | fails | passes |
232 | fails | fails |
233 """
234 When I run "behave -f plain features/two_undefined_step_in_scenario_outline.feature"
235 Then it should fail with:
236 """
237 0 features passed, 1 failed, 0 skipped
238 0 scenarios passed, 4 failed, 0 skipped
239 2 steps passed, 2 failed, 4 skipped, 8 undefined
240 """
241 And undefined-step snippets should exist for:
242 | Step |
243 | When an undefined step is used |
244 | Then another undefined step is used |
245
246
247 Scenario: Undefined steps are detected if scenario is selected via tag
248 Given a file named "features/undefined_steps_with_tagged_scenario.feature" with:
249 """
250 Feature:
251
252 @selected
253 Scenario: S1
254 Given a step passes
255 And an undefined step Alice
256 When a step fails
257 Then an undefined step Bob
258
259 @selected
260 Scenario: S2
261 Given a step passes
262 When an undefined step Charly
263
264 @not_selected
265 Scenario: S3
266 Given an undefined step Delta
267 Then a step fails
268 """
269 When I run "behave -f plain --tags=@selected features/undefined_steps_with_tagged_scenario.feature"
270 Then it should fail with:
271 """
272 0 features passed, 1 failed, 0 skipped
273 0 scenarios passed, 2 failed, 1 skipped
274 2 steps passed, 0 failed, 3 skipped, 3 undefined
275 """
276 And undefined-step snippets should exist for:
277 | Step |
278 | Given an undefined step Alice |
279 | Then an undefined step Bob |
280 | When an undefined step Charly |
281 But undefined-step snippets should not exist for:
282 | Step |
283 | Given a step passes |
284 | Given an undefined step Delta |
285 | When a step fails |
286 | Then a step fails |
287
288
289 Scenario: Undefined steps are detected if --dry-run option is used
290 When I run "behave -f plain --dry-run features/undefined_steps_with_tagged_scenario.feature"
291 Then it should fail with:
292 """
293 0 features passed, 0 failed, 0 skipped, 1 untested
294 0 scenarios passed, 0 failed, 0 skipped, 3 untested
295 0 steps passed, 0 failed, 0 skipped, 4 undefined, 4 untested
296 """
297 And undefined-step snippets should exist for:
298 | Step |
299 | Given an undefined step Alice |
300 | Then an undefined step Bob |
301 | When an undefined step Charly |
302 | Given an undefined step Delta |
303 But undefined-step snippets should not exist for:
304 | Step |
305 | Given a step passes |
306 | When a step fails |
307 | Then a step fails |