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

Merge branch 'master' into fix_tags_tests

This commit is contained in:
Milosz Sliwinski 2019-01-13 11:07:28 +01:00 committed by GitHub
parent 07efb553d4 ad844ffb11
commit cb8114bbbe
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
README.rst
View File

@ -11,18 +11,18 @@ BDD library for the py.test runner
:target: https://readthedocs.org/projects/pytest-bdd/?badge=latest :target: https://readthedocs.org/projects/pytest-bdd/?badge=latest
:alt: Documentation Status :alt: Documentation Status
pytest-bdd implements a subset of Gherkin language for the automation of the project pytest-bdd implements a subset of the Gherkin language to enable automating project
requirements testing and easier behavioral driven development. requirements testing and to facilitate behavioral driven development.
Unlike many other BDD tools it doesn't require a separate runner and benefits from Unlike many other BDD tools, it does not require a separate runner and benefits from
the power and flexibility of the pytest. It allows to unify your unit and functional the power and flexibility of pytest. It enables unifying unit and functional
tests, easier continuous integration server configuration and maximal reuse of the tests, reduces the burden of continuous integration server configuration and allows the reuse of
tests setup. test setups.
Pytest fixtures written for the unit tests can be reused for the setup and actions Pytest fixtures written for unit tests can be reused for setup and actions
mentioned in the feature steps with dependency injection, which allows a true BDD mentioned in feature steps with dependency injection. This allows a true BDD
just-enough specification of the requirements without maintaining any context object just-enough specification of the requirements without maintaining any context object
containing the side effects of the Gherkin imperative declarations. containing the side effects of Gherkin imperative declarations.
.. _behave: https://pypi.python.org/pypi/behave .. _behave: https://pypi.python.org/pypi/behave
.. _pytest-splinter: https://github.com/pytest-dev/pytest-splinter .. _pytest-splinter: https://github.com/pytest-dev/pytest-splinter
@ -35,7 +35,7 @@ Install pytest-bdd
pip install pytest-bdd pip install pytest-bdd
The minimal required version of pytest is 2.8.1. The minimum required version of pytest is 2.8.1.
Example Example
@ -107,13 +107,13 @@ test_publish_article.py:
Scenario decorator Scenario decorator
------------------ ------------------
Scenario decorator can accept such optional keyword arguments: The scenario decorator can accept the following optional keyword arguments:
* ``encoding`` - decode content of feature file in specific encoding. UTF-8 is default. * ``encoding`` - decode content of feature file in specific encoding. UTF-8 is default.
* ``example_converters`` - mapping to pass functions to convert example values provided in feature files. * ``example_converters`` - mapping to pass functions to convert example values provided in feature files.
Function decorated with `scenario` decorator behaves like a normal test function, Functions decorated with the `scenario` decorator behave like a normal test function,
which will be executed after all scenario steps. and they will be executed after all scenario steps.
You can consider it as a normal pytest test function, e.g. order fixtures there, You can consider it as a normal pytest test function, e.g. order fixtures there,
call other functions and make assertions: call other functions and make assertions:
@ -130,7 +130,7 @@ call other functions and make assertions:
Step aliases Step aliases
------------ ------------
Sometimes it is needed to declare the same fixtures or steps with the Sometimes, one has to declare the same fixtures or steps with
different names for better readability. In order to use the same step different names for better readability. In order to use the same step
function with multiple step names simply decorate it multiple times: function with multiple step names simply decorate it multiple times: