| 1 |
@issue |
| 2 |
Feature: Issue #181: Escape apostrophes in undefined steps snippets |
| 3 |
|
| 4 |
. I have noticed that, for the following line in my features file: |
| 5 |
. |
| 6 |
. Then I'm redirected to http://www.example.com |
| 7 |
. |
| 8 |
. Behave outputs the following: |
| 9 |
. |
| 10 |
. @then(u'I'm redirected to http://www.example.com') |
| 11 |
. def step_impl(context): |
| 12 |
. assert False |
| 13 |
|
| 14 |
|
| 15 |
Scenario: |
| 16 |
Given a new working directory |
| 17 |
And an empty file named "features/steps/steps.py" |
| 18 |
And a file named "features/issue181_example.feature" with |
| 19 |
""" |
| 20 |
Feature: |
| 21 |
Scenario: |
| 22 |
Given I'm using an "undefined step" |
| 23 |
""" |
| 24 |
When I run "behave -f plain features/issue181_example.feature" |
| 25 |
Then it should fail with: |
| 26 |
""" |
| 27 |
0 steps passed, 0 failed, 0 skipped, 1 undefined |
| 28 |
""" |
| 29 |
And the command output should contain: |
| 30 |
""" |
| 31 |
You can implement step definitions for undefined steps with these snippets: |
| 32 |
|
| 33 |
@given(u'I\'m using an "undefined step"') |
| 34 |
def step_impl(context): |
| 35 |
raise NotImplementedError(u'STEP: Given I\'m using an "undefined step"') |
| 36 |
""" |