zeman
/
pytest-bdd
forked from test_framework/pytest-bdd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #239 from felixonmars/patch-1 

Fix some typos in README
This commit is contained in:
Florian Bruhin 2018-06-04 08:55:15 +02:00 committed by GitHub
parent 5684b36532 11df9bf712
commit 0527a9623f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.rst
View File

@ -392,7 +392,7 @@ But in much cleaner and powerful way:
Then the text should be parsed with correct indentation
Step is considered as multiline one, if the **next** line(s) after it's first line, is indented relatively
to the first line. The step name is then simply extended by adding futher lines with newlines.
to the first line. The step name is then simply extended by adding further lines with newlines.
In the example above, the Given step name will be:
.. code-block:: python
@ -723,7 +723,7 @@ completely different:
For picking up tests to run we can use
`tests selection <http://pytest.org/latest/usage.html#specifying-tests-selecting-tests>`_ technique. The problem is that
you have to know how your tests are organized, knowing ony the feature files organization is not enough.
you have to know how your tests are organized, knowing only the feature files organization is not enough.
`cucumber tags <https://github.com/cucumber/cucumber/wiki/Tags>`_ introduce standard way of categorizing your features
and scenarios, which pytest-bdd supports. For example, we could have:
@ -1080,7 +1080,7 @@ test_publish_article.py:
return False
@scenario('publish_article.feature', 'Publishing the article in a wierd way')
@scenario('publish_article.feature', 'Publishing the article in a weird way')
def test_publish():
pass