forked from test_framework/pytest-bdd
Remove reason from documentation
This commit is contained in:
parent
4826aa06d9
commit
e9d1f11af3
|
@ -1217,8 +1217,7 @@ ordering of the types of the steps.
|
||||||
Migration of your tests from versions 2.x.x
|
Migration of your tests from versions 2.x.x
|
||||||
------------------------------------------------
|
------------------------------------------------
|
||||||
|
|
||||||
In version 3.0.0, the fixtures ``pytestbdd_feature_base_dir`` and ``pytestbdd_strict_gherkin`` have been removed. The reason for it is that those fixtures had to be evaluated at module import time, but fixtures are not meant to invoked directly.
|
In version 3.0.0, the fixtures ``pytestbdd_feature_base_dir`` and ``pytestbdd_strict_gherkin`` have been removed.
|
||||||
Pytest is going to not allow calling fixtures directly in version 4.
|
|
||||||
|
|
||||||
If you used ``pytestbdd_feature_base_dir`` fixture to override the path discovery, you can instead configure it in ``pytest.ini``:
|
If you used ``pytestbdd_feature_base_dir`` fixture to override the path discovery, you can instead configure it in ``pytest.ini``:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue