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
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
Feature: Internationalization (i18n) and Problems with Unicode Strings
. POTENTIAL PROBLEM AREAS:
. * Feature, scenario, step names with problematic chars
. * Tags with problematic chars
. * step raises exception with problematic text (output capture)
. * step generates output with problematic and some step fails (stdout capture)
. * filenames with problematic chars: feature files, steps files
.
. CHECKED FORMATTERS and REPORTERS:
. * plain
. * pretty
. * junit (used via "behave.ini" defaults)
@setup
Scenario: Feature Setup
Given a new working directory
And a file named "behave.ini" with:
"""
[behave]
show_timings = false
show_skipped = false
show_source = true
junit = true
"""
And a file named "features/steps/passing_steps.py" with:
"""
# -*- coding: UTF-8 -*-
from behave import step
@step(u'{word:w} step passes')
def step_passes(context, word):
pass
@step(u'{word:w} step passes with "{text}"')
def step_passes_with_text(context, word, text):
pass
@step(u'{word:w} step fails')
def step_fails(context, word):
assert False, "XFAIL"
@step(u'{word:w} step fails with "{text}"')
def step_fails_with_text(context, word, text):
assert False, u"XFAIL: "+ text
"""
And a file named "features/steps/step_write_output.py" with:
"""
# -*- coding: UTF-8 -*-
from __future__ import print_function
from behave import step
import six
@step(u'I write text "{text}" to stdout')
def step_write_text(context, text):
if six.PY2 and isinstance(text, six.text_type):
text = text.encode("utf-8", "replace")
print(text)
@step(u'I write bytes "{data}" to stdout')
def step_write_bytes(context, data):
if isinstance(data, six.text_type):
data = data.encode("unicode-escape", "replace")
print(data)
"""
Scenario Outline: Problematic scenario name: <scenario.name> (case: passed, <format>)
Given a file named "features/scenario_name_problematic_and_pass.feature" with:
"""
Feature:
Scenario: <scenario.name>
Given a step passes
"""
When I run "behave -f <format> features/scenario_name_problematic_and_pass.feature"
Then it should pass with:
"""
1 feature passed, 0 failed, 0 skipped
1 scenario passed, 0 failed, 0 skipped
"""
And the command output should contain:
"""
Scenario: <scenario.name>
"""
Examples:
| format | scenario.name |
| plain | Café |
| pretty | Ärgernis ist überall |
Scenario Outline: Problematic scenario name: <scenario.name> (case: failed, <format>)
Given a file named "features/scenario_name_problematic_and_fail.feature" with:
"""
Feature:
Scenario: <scenario.name>
Given a step fails
"""
When I run "behave -f <format> features/scenario_name_problematic_and_fail.feature"
Then it should fail with:
"""
0 features passed, 1 failed, 0 skipped
0 scenarios passed, 1 failed, 0 skipped
"""
And the command output should contain:
"""
Scenario: <scenario.name>
"""
Examples:
| format | scenario.name |
| plain | Café |
| pretty | Ärgernis ist überall |
Scenario Outline: Problematic step: <step.text> (case: passed, <format>)
Given a file named "features/step_problematic_and_pass.feature" with:
"""
Feature:
Scenario:
Given a step passes with "<step.text>"
"""
When I run "behave -f <format> features/step_problematic_and_pass.feature"
Then it should pass with:
"""
1 feature passed, 0 failed, 0 skipped
1 scenario passed, 0 failed, 0 skipped
1 step passed, 0 failed, 0 skipped, 0 undefined
"""
Examples:
| format | step.text |
| plain | Café |
| pretty | Ärgernis ist überall |
Scenario Outline: Problematic step: <step.text> (case: fail, <format>)
Given a file named "features/step_problematic_and_fail.feature" with:
"""
Feature:
Scenario:
Given a step fails with "<step.text>"
"""
When I run "behave -f <format> features/step_problematic_and_fail.feature"
Then it should fail with:
"""
0 features passed, 1 failed, 0 skipped
0 scenarios passed, 1 failed, 0 skipped
0 steps passed, 1 failed, 0 skipped, 0 undefined
"""
Examples:
| format | step.text |
| plain | Café |
| pretty | Ärgernis ist überall |
@problematic.feature_filename
@not.with_os=win32
Scenario Outline: Problematic feature filename: <name> (case: pass, <format>)
Given a file named "features/<name>_and_pass.feature" with:
"""
Feature:
Scenario:
Given a step passes
"""
When I run "behave -f <format> features/<name>_and_pass.feature"
Then it should pass with:
"""
1 feature passed, 0 failed, 0 skipped
1 scenario passed, 0 failed, 0 skipped
"""
Examples:
| format | name |
| plain | Café |
| pretty | Ärgernis_ist_überall |
@problematic.feature_filename
@not.with_os=win32
Scenario Outline: Problematic feature filename: <name> (case: fail, <format>)
Given a file named "features/<name>_and_fail.feature" with:
"""
Feature:
Scenario:
Given a step fails
"""
When I run "behave -f <format> features/<name>_and_fail.feature"
Then it should fail with:
"""
0 features passed, 1 failed, 0 skipped
0 scenarios passed, 1 failed, 0 skipped
"""
Examples:
| format | name |
| plain | Café |
| pretty | Ärgernis_ist_überall |
@problematic.step_filename
Scenario Outline: Problematic step filename: <name> (case: pass, <format>)
TEST-CONSTRAINT: Only one step file is used (= 1 name only).
Otherwise, duplicated steps occur (without cleanup in step directory).
Given a file named "features/problematic_stepfile_and_pass.feature" with:
"""
Feature:
Scenario:
Given I use a weird step and pass
"""
And a file named "features/steps/step_pass_<name>.py" with:
"""
from behave import step
@step(u'I use a weird step and pass')
def step_weird_pass(context):
pass
"""
When I run "behave -f <format> features/problematic_stepfile_and_pass.feature"
Then it should pass with:
"""
1 feature passed, 0 failed, 0 skipped
1 scenario passed, 0 failed, 0 skipped
"""
But note that "you should normally use only ASCII/latin-1 python filenames"
Examples:
| format | name |
| plain | Ärgernis_ist_überall |
| pretty | Ärgernis_ist_überall |
@problematic.step_filename
Scenario Outline: Problematic step filename: <name> (case: fail, <format>)
TEST-CONSTRAINT: Only one step file is used (= 1 name only).
Otherwise, duplicated steps occur (without cleanup in step directory).
Given a file named "features/problematic_stepfile_and_fail.feature" with:
"""
Feature:
Scenario:
Given I use a weird step and fail
"""
And a file named "features/steps/step_fail_<name>.py" with:
"""
from behave import step
@step(u'I use a weird step and fail')
def step_weird_fails(context):
assert False, "XFAIL-WEIRD"
"""
When I run "behave -f <format> features/problematic_stepfile_and_fail.feature"
Then it should fail with:
"""
0 features passed, 1 failed, 0 skipped
0 scenarios passed, 1 failed, 0 skipped
"""
But note that "you should normally use only ASCII/latin-1 python filenames"
Examples:
| format | name |
| plain | Ärgernis_ist_überall |
| pretty | Ärgernis_ist_überall |
@problematic.output
Scenario Outline: Problematic output: <text> (case: pass, <format>)
Given a file named "features/problematic_output_and_pass.feature" with:
"""
Feature:
Scenario:
Given I write text "<text>" to stdout
Then I write bytes "<text>" to stdout
And a step passes
"""
When I run "behave -f <format> --no-capture features/problematic_output_and_pass.feature"
Then it should pass with:
"""
1 feature passed, 0 failed, 0 skipped
1 scenario passed, 0 failed, 0 skipped
"""
Examples:
| format | text |
| plain | Café |
| pretty | Ärgernis ist überall |
@problematic.output
Scenario Outline: Problematic output: <text> (case: fail, <format>)
Given a file named "features/problematic_output_and_fail.feature" with:
"""
Feature:
Scenario:
Given I write text "<text>" to stdout
Then I write bytes "<text>" to stdout
And a step fails
"""
When I run "behave -f <format> features/problematic_output_and_fail.feature"
Then it should fail with:
"""
0 features passed, 1 failed, 0 skipped
0 scenarios passed, 1 failed, 0 skipped
"""
And the command output should contain:
"""
<text>
"""
Examples:
| format | text |
| plain | Café |
| pretty | Ärgernis ist überall |
@problematic.tags
Scenario Outline: Problematic tag: <tag> (case: pass, <format>)
Given a file named "features/problematic_tag_and_pass.feature" with:
"""
Feature:
@<tag>
Scenario:
Given a step passes
"""
When I run "behave -f <format> features/problematic_tag_and_pass.feature"
Then it should pass with:
"""
1 scenario passed, 0 failed, 0 skipped
"""
Examples:
| format | tag |
| plain | tag.Café |
| pretty | tag.Ärgernis_ist_überall |
@problematic.tags
Scenario Outline: Problematic tag: <tag> (case: fail, <format>)
Given a file named "features/problematic_tag_and_fail.feature" with:
"""
Feature:
@<tag>
Scenario:
Given a step fails
"""
When I run "behave -f <format> features/problematic_tag_and_fail.feature"
Then it should fail with:
"""
0 scenarios passed, 1 failed, 0 skipped
"""
Examples:
| format | tag |
| plain | tag.Café |
| pretty | tag.Ärgernis_ist_überall |
@issue_0230
Scenario Outline: Step assert fails with problematic chars (case: <format>)
NOTE: Python2 fails silently without showing the failed step.
HINT: Use unicode string when you use, special non-ASCII characters.
HINT: Use encoding-hint in python file header.
Given a file named "features/steps/problematic_steps.py" with:
"""
# -*- coding: UTF-8 -*-
from behave import step
@step(u'{word:w} step fails with assert and non-ASCII text')
def step_fails_with_assert_and_problematic_text(context, word):
assert False, u"XFAIL:¾;"
"""
And a file named "features/assert_with_ptext.feature" with:
"""
Feature:
Scenario:
Given a step passes
When a step fails with assert and non-ASCII text
"""
When I run "behave -f <format> features/assert_with_ptext.feature"
Then it should fail with:
"""
0 scenarios passed, 1 failed, 0 skipped
1 step passed, 1 failed, 0 skipped, 0 undefined
"""
And the command output should contain:
"""
Assertion Failed: XFAIL:¾;
"""
Examples:
| format |
| plain |
| pretty |
@issue_0226
Scenario Outline: Step raises exception with problematic chars (case: <format>)
In Python2: When an exception is raised with unicode argument,
(and special non-ASCII chars) the conversion of the exception into
a unicode string causes implicit conversion into a normal string
by using the default encoding (normally: ASCII).
Therefore, the implicit encoding into a normal string often fails.
SEE ALSO: http://bugs.python.org/issue2517
NOTE: Better if encoding hint is provided in python file header.
Given a file named "features/steps/problematic_steps.py" with:
"""
# -*- coding: UTF-8 -*-
from behave import step
@step(u'{word:w} step fails with exception and non-ASCII text')
def step_fails_with_exception_and_problematic_text(context, word):
# -- REQUIRE: UNICODE STRING, when special, non-ASCII chars are used.
raise RuntimeError(u"FAIL:¾;")
"""
And a file named "features/exception_with_ptext.feature" with:
"""
Feature:
Scenario:
Given a step passes
When a step fails with exception and non-ASCII text
"""
When I run "behave -f <format> features/exception_with_ptext.feature"
Then it should fail with:
"""
0 scenarios passed, 1 failed, 0 skipped
1 step passed, 1 failed, 0 skipped, 0 undefined
"""
And the command output should contain:
"""
RuntimeError: FAIL:¾;
"""
Examples:
| format |
| plain |
| pretty |
|
