Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==4.1.0
->==6.1.1
Release Notes
pytest-dev/pytest-bdd (pytest-bdd)
v6.1.1
Compare Source
pytest_bdd_after_scenario
hook would be called after every step instead of after the scenario.#​577 <https://github.com/pytest-dev/pytest-bdd/pull/577>
_v6.1.0
Compare Source
#​534 <https://github.com/pytest-dev/pytest-bdd/pull/534>
_converters
andtarget_fixture
every at every application.#​534 <https://github.com/pytest-dev/pytest-bdd/pull/534>
_#​544 <https://github.com/pytest-dev/pytest-bdd/pull/544>
_#​525 <https://github.com/pytest-dev/pytest-bdd/issues/525>
_#​534 <https://github.com/pytest-dev/pytest-bdd/pull/534>
_step
decorator that will be used for all kind of steps#​548 <https://github.com/pytest-dev/pytest-bdd/pull/548>
_stacklevel
param togiven
,when
,then
,step
decorators. This allows for programmatic step generation#​548 <https://github.com/pytest-dev/pytest-bdd/pull/548>
_#​557 <https://github.com/pytest-dev/pytest-bdd/pull/557>
_.#​559 <https://github.com/pytest-dev/pytest-bdd/issues/559>
_#​563 <https://github.com/pytest-dev/pytest-bdd/pull/563>
_.bdd_features_base_dir
is interpreted as relative to thepytest root directory <https://docs.pytest.org/en/latest/reference/customize.html#rootdir>
_ (previously it was relative to the current working directory).#​573 <https://github.com/pytest-dev/pytest-bdd/pull/573>
_v6.0.1
Compare Source
#​530 <https://github.com/pytest-dev/pytest-bdd/pull/530>
_#​528 <https://github.com/pytest-dev/pytest-bdd/issues/528>
_v6.0.0
Compare Source
This release introduces breaking changes in order to be more in line with the official gherkin specification.
#​469 <https://github.com/pytest-dev/pytest-bdd/pull/469>
_#​490 <https://github.com/pytest-dev/pytest-bdd/pull/490>
_#​492 <https://github.com/pytest-dev/pytest-bdd/pull/492>
_#​493 <https://github.com/pytest-dev/pytest-bdd/pull/493>
_#​495 <https://github.com/pytest-dev/pytest-bdd/pull/495>
_#​504 <https://github.com/pytest-dev/pytest-bdd/issues/504>
_#​503 <https://github.com/pytest-dev/pytest-bdd/issues/503>
_#​499 <https://github.com/pytest-dev/pytest-bdd/pull/499>
_#​505 <https://github.com/pytest-dev/pytest-bdd/pull/505>
_pytest_bdd.parsers.StepParser
now is an Abstract Base Class. Subclasses must make sure to implement the abstract methods. (youtux)#​505 <https://github.com/pytest-dev/pytest-bdd/pull/505>
_#​524 <https://github.com/pytest-dev/pytest-bdd/pull/524>
_.v5.0.0
Compare Source
This release introduces breaking changes, please refer to the :ref:
Migration from 4.x.x
.@given("there are <start> cucumbers")
and@given(parsers.parse("there are {start} cucumbers"))
. The latter will be enough.example_converters
fromscenario(...)
signature. You should now use just theconverters
parameter forgiven
,when
,then
.--cucumberjson-expanded
and--cucumber-json-expanded
options. Now the JSON report is always expanded.--gherkin-terminal-reporter-expanded
option. Now the terminal report is always expanded.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.