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
|
@issue
Feature: Issue #73: the current_matcher is not predictable
. behave provides 2 matchers: ParseMatcher (parse) and RegexpMatcher (re).
. The ParseMatcher is used per default when the test runner starts.
.
. A step definition file may change the matcher several times
. by calling `use_step_matcher("re")` or `use_step_matcher("parse")`.
. In order to make the writing of step definitions more predictable,
. the matcher should be reset to the default matcher
. before loading each step definition.
.
. A project can define its own default matcher by calling the
. `use_step_matcher(...)` in the "environment.py" hook.
. This matcher will be used as default before a step definition is loaded.
Scenario: Verify that ParseMatcher is the default matcher
Given a new working directory
And a file named "features/steps/parse_steps.py" with:
"""
from behave import step
@step(u'a step {outcome:w}')
def step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
"""
And a file named "features/passing.feature" with:
"""
Feature:
Scenario:
Given a step passes
When a step passes
Then a step passes
"""
When I run "behave -f plain features/passing.feature"
Then it should pass with
"""
1 scenario passed, 0 failed, 0 skipped
3 steps passed, 0 failed, 0 skipped, 0 undefined
"""
Scenario: Use only RegexMatcher in Step Definitions
Given a new working directory
And a file named "features/environment.py" with:
"""
from behave import use_step_matcher
use_step_matcher("re")
"""
And a file named "features/steps/regexp_steps.py" with:
"""
from behave import step
@step(u'a step (?P<outcome>passes|fails)')
def step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
"""
And a file named "features/passing.feature" with:
"""
Feature:
Scenario:
Given a step passes
When a step passes
Then a step passes
"""
When I run "behave -f plain features/passing.feature"
Then it should pass with
"""
1 scenario passed, 0 failed, 0 skipped
3 steps passed, 0 failed, 0 skipped, 0 undefined
"""
Scenario: Use ParseMatcher and RegexMatcher in Step Definitions (default=re)
Given a new working directory
And a file named "features/environment.py" with:
"""
from behave import use_step_matcher
use_step_matcher("re")
"""
And a file named "features/steps/eparse_steps.py" with:
"""
from behave import step, use_step_matcher
use_step_matcher("parse")
@step(u'an extraordinary step {outcome:w}')
def step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
"""
And a file named "features/steps/regexp_steps.py" with:
"""
from behave import step
@step(u'a step (?P<outcome>passes|fails)')
def step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
"""
And a file named "features/steps/xparse_steps.py" with:
"""
from behave import step, use_step_matcher
use_step_matcher("parse")
@step(u'another step {outcome:w}')
def step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
"""
And a file named "features/passing3.feature" with:
"""
Feature:
Scenario:
Given a step passes
When another step passes
Then an extraordinary step passes
"""
When I run "behave -f plain features/passing3.feature"
Then it should pass with
"""
1 scenario passed, 0 failed, 0 skipped
3 steps passed, 0 failed, 0 skipped, 0 undefined
"""
Scenario: Mix ParseMatcher and RegexMatcher in Step Definitions (default=re)
Given a new working directory
And a file named "features/environment.py" with:
"""
from behave import use_step_matcher
use_step_matcher("re")
"""
And a file named "features/steps/given_steps.py" with:
"""
from behave import step, use_step_matcher
use_step_matcher("parse")
@given(u'a step {outcome:w}')
def given_step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
use_step_matcher("re")
@given(u'another step (?P<outcome>passes|fails)')
def given_another_step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
use_step_matcher("parse")
@given(u'an extraordinary step {outcome:w}')
def given_extraordinary_step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
"""
And a file named "features/steps/when_steps.py" with:
"""
from behave import step, use_step_matcher
@when(u'a step (?P<outcome>passes|fails)')
def when_step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
use_step_matcher("parse")
@when(u'another step {outcome:w}')
def when_another_step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
use_step_matcher("re")
@when(u'an extraordinary step (?P<outcome>passes|fails)')
def when_extraordinary_step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
"""
And a file named "features/steps/then_steps.py" with:
"""
from behave import step, use_step_matcher
use_step_matcher("parse")
@then(u'a step {outcome:w}')
def then_step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
use_step_matcher("re")
@then(u'another step (?P<outcome>passes|fails)')
def then_another_step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
use_step_matcher("parse")
@then(u'an extraordinary step {outcome:w}')
def then_extraordinary_step_passes(context, outcome):
assert outcome == "passes", "FAIL: outcome={0}".format(outcome)
"""
And a file named "features/passing3.feature" with:
"""
Feature:
Scenario: 1
Given a step passes
When another step passes
Then an extraordinary step passes
Scenario: 2
Given another step passes
When an extraordinary step passes
Then a step passes
Scenario: 3
Given an extraordinary step passes
When a step passes
Then another step passes
"""
When I run "behave -c -f pretty --no-timings features/passing3.feature"
Then it should pass with:
"""
3 scenarios passed, 0 failed, 0 skipped
9 steps passed, 0 failed, 0 skipped, 0 undefined
"""
And the command output should contain:
"""
Feature: # features/passing3.feature:1
Scenario: 1 # features/passing3.feature:2
Given a step passes # features/steps/given_steps.py:4
When another step passes # features/steps/when_steps.py:8
Then an extraordinary step passes # features/steps/then_steps.py:14
Scenario: 2 # features/passing3.feature:7
Given another step passes # features/steps/given_steps.py:9
When an extraordinary step passes # features/steps/when_steps.py:13
Then a step passes # features/steps/then_steps.py:4
Scenario: 3 # features/passing3.feature:12
Given an extraordinary step passes # features/steps/given_steps.py:14
When a step passes # features/steps/when_steps.py:3
Then another step passes # features/steps/then_steps.py:9
"""
|
