File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -392,7 +392,7 @@ But in much cleaner and powerful way:
392
392
Then the text should be parsed with correct indentation
393
393
394
394
Step is considered as multiline one, if the **next ** line(s) after it's first line, is indented relatively
395
- to the first line. The step name is then simply extended by adding futher lines with newlines.
395
+ to the first line. The step name is then simply extended by adding further lines with newlines.
396
396
In the example above, the Given step name will be:
397
397
398
398
.. code-block :: python
@@ -723,7 +723,7 @@ completely different:
723
723
724
724
For picking up tests to run we can use
725
725
`tests selection <http://pytest.org/latest/usage.html#specifying-tests-selecting-tests >`_ technique. The problem is that
726
- you have to know how your tests are organized, knowing ony the feature files organization is not enough.
726
+ you have to know how your tests are organized, knowing only the feature files organization is not enough.
727
727
`cucumber tags <https://github.com/cucumber/cucumber/wiki/Tags >`_ introduce standard way of categorizing your features
728
728
and scenarios, which pytest-bdd supports. For example, we could have:
729
729
@@ -1080,7 +1080,7 @@ test_publish_article.py:
1080
1080
return False
1081
1081
1082
1082
1083
- @scenario (' publish_article.feature' , ' Publishing the article in a wierd way' )
1083
+ @scenario (' publish_article.feature' , ' Publishing the article in a weird way' )
1084
1084
def test_publish ():
1085
1085
pass
1086
1086
You can’t perform that action at this time.
0 commit comments