-
Aside from the standard unit tests, PyTest has a BDD [library](https://pytest-bdd.readthedocs.org/en/latest/).
-
it should put a "# coding: utf-8" in the beginning of the file.
-
The documentation on https://github.com/pytest-dev/pytest-bdd#multiline-steps (https://github.com/pytest-dev/pytest-bdd/blame/master/README.rst#L317-L321) seems to be wrong:
```
@then('the text shoul…
-
This causes the entire scenario to be replayed rather than the parameterized steps.
Would it be possible to provide a hint to use parameterize?
-
I'm not sure but probably `pytest` command is somehow not used (legacy?). Pytest is using now `py.test` as entrypoint.
I think pytest-bdd could use plugins to integrate with py.test (like other plugin…
-
There should be a way to escape a # or even better, if it is inside quotes or on a table it should be treated as data.
-
To reproduce:
```
virtualenv bdd -p python3.4 && bdd/bin/pip install pytest-bdd && bdd/bin/pytest-bdd
```
Output:
```
Traceback (most recent call last):
File "bdd/bin/pytest-bdd", line 9, in
…
-
Given a [this directory structure](http://goo.gl/CKbc9x) and [this feature file](https://github.com/jaymartin7/pytest_trace/blob/master/tracepkg/features/feature1.feature):
When I run `pytest-bdd gen…
-
Tests are created using `@scenario` decorator and after that the function has to be written (with unique function name). So basically test name exist in 3 places, feature file, decorator and (kind of)…
-
When the test is not implemented they are not executed without a warning.
I can imagine scenario like:
1. I have a feature file with scenario "This is my scenario"
2. I have implemented scenario with:…