Skip to content

Commit 8312d69

Browse files
committed
More fixes
1 parent 4325a3e commit 8312d69

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

README.rst

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Install `pytest-bdd` using `pip`:
3232
Example
3333
-------
3434

35-
An example test for a blog hosting software could look like this. Note that pytest-splinter_ is used to get the is used to get the browser fixture.
35+
An example test for a blog hosting software could look like this. Note that pytest-splinter_ is used to get the browser fixture.
3636

3737
.. code-block:: gherkin
3838
@@ -83,7 +83,7 @@ An example test for a blog hosting software could look like this. Note that pyte
8383
assert article.is_published
8484
8585
Declaring tests in python files
86-
------------------
86+
-------------------------------
8787
The recommended approach to run tests defined by feature files is to create a python test module for each feature file, and define the step implementation within the module:
8888

8989
.. code-block:: python
@@ -100,7 +100,6 @@ The recommended approach to run tests defined by feature files is to create a py
100100
101101
...
102102
103-
104103
You can also decide to collect all the feature files found in a directory. For example, this will collect all the feature files from the `features` folder recursively:
105104

106105
.. code-block:: python
@@ -232,7 +231,7 @@ Example with `re` parser
232231
Implementing a custom step parser
233232
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
234233

235-
You can implement your own step parser. It's interface is quite simple. The code can look like:
234+
You can implement your own step parser. Its interface is quite simple. The code can look like:
236235

237236
.. code-block:: python
238237
@@ -258,7 +257,7 @@ You can implement your own step parser. It's interface is quite simple. The code
258257
return {"count": int(start)}
259258
260259
Override fixtures (injection)
261-
---------------------------------
260+
-----------------------------
262261

263262
To imperatively change a fixture only for certain tests (scenarios), use the ``target_fixture`` parameter in the `given` decorator:
264263

@@ -559,7 +558,7 @@ features.
559558
560559
Scenario: Greg posts to a client's blog
561560
Given I am logged in as Greg
562-
When I try to post to "Expensive Therapy"
561+
When I try to post to "Expensive Therapy"
563562
Then I should see "Your article was published."
564563
565564
In this example, all steps from the background will be executed before all the scenario's own given

0 commit comments

Comments
 (0)