build(deps): bump pytest-bdd from 4.0.2 to 6.1.1 in /testing/plugins_integration

[dependabot]

Bumps pytest-bdd from 4.0.2 to 6.1.1.

Release notes

Sourced from pytest-bdd's releases.

Release 6.1.1

Full Changelog: pytest-dev/pytest-bdd@6.1.0...6.1.1

Release 6.0.0

This release introduces breaking changes in order to be more in line with the official gherkin specification.

• Cleanup of the documentation and tests related to parametrization (elchupanebrej) pytest-dev/pytest-bdd#469
• Removed feature level examples for the gherkin compatibility (olegpidsadnyi) pytest-dev/pytest-bdd#490
• Removed vertical examples for the gherkin compatibility (olegpidsadnyi) pytest-dev/pytest-bdd#492
• Step arguments are no longer fixtures (olegpidsadnyi) pytest-dev/pytest-bdd#493
• Drop support of python 3.6, pytest 4 (elchupanebrej) pytest-dev/pytest-bdd#495 pytest-dev/pytest-bdd#504
• Step definitions can have "yield" statements again (4.0 release broke it). They will be executed as normal fixtures: code after the yield is executed during teardown of the test. (youtux) pytest-dev/pytest-bdd#503
• Scenario outlines unused example parameter validation is removed (olegpidsadnyi) pytest-dev/pytest-bdd#499
• Add type annotations (youtux) pytest-dev/pytest-bdd#505
• pytest_bdd.parsers.StepParser now is an Abstract Base Class. Subclasses must make sure to implement the abstract methods. (youtux) pytest-dev/pytest-bdd#505
• Angular brackets in step definitions are only parsed in "Scenario Outline" (previously they were parsed also in normal "Scenario"s) (youtux) pytest-dev/pytest-bdd#524.

Release 5.0.0

• Rewrite the logic to parse Examples for Scenario Outlines. Now the substitution of the examples is done during the parsing of Gherkin feature files. You won't need to define the steps twice like @given("there are <start> cucumbers") and @given(parsers.parse("there are {start} cucumbers")). The latter will be enough.
• Removed example_converters from scenario(...) signature. You should now use just the converters parameter for given, when, then.
• Removed --cucumberjson-expanded and --cucumber-json-expanded options. Now the JSON report is always expanded.
• Removed --gherkin-terminal-reporter-expanded option. Now the terminal report is always expanded.

Changelog

Sourced from pytest-bdd's changelog.

6.1.1

• Fix regression introduced in version 6.1.0 where the pytest_bdd_after_scenario hook would be called after every step instead of after the scenario. [#577](https://github.com/pytest-dev/pytest-bdd/issues/577) <https://github.com/pytest-dev/pytest-bdd/pull/577>_

6.1.0

• Fix bug where steps without parsers would take precedence over steps with parsers. [#534](https://github.com/pytest-dev/pytest-bdd/issues/534) <https://github.com/pytest-dev/pytest-bdd/pull/534>_
• Step functions can now be decorated multiple times with @​given, @​when, @​then. Previously every decorator would override converters and target_fixture every at every application. [#534](https://github.com/pytest-dev/pytest-bdd/issues/534) <https://github.com/pytest-dev/pytest-bdd/pull/534>_ [#544](https://github.com/pytest-dev/pytest-bdd/issues/544) <https://github.com/pytest-dev/pytest-bdd/pull/544>_ [#525](https://github.com/pytest-dev/pytest-bdd/issues/525) <https://github.com/pytest-dev/pytest-bdd/issues/525>_
• Require pytest>=6.2 [#534](https://github.com/pytest-dev/pytest-bdd/issues/534) <https://github.com/pytest-dev/pytest-bdd/pull/534>_
• Using modern way to specify hook options to avoid deprecation warnings with pytest >=7.2.
• Add generic step decorator that will be used for all kind of steps [#548](https://github.com/pytest-dev/pytest-bdd/issues/548) <https://github.com/pytest-dev/pytest-bdd/pull/548>_
• Add stacklevel param to given, when, then, step decorators. This allows for programmatic step generation [#548](https://github.com/pytest-dev/pytest-bdd/issues/548) <https://github.com/pytest-dev/pytest-bdd/pull/548>_
• Hide pytest-bdd internal method in user tracebacks [#557](https://github.com/pytest-dev/pytest-bdd/issues/557) <https://github.com/pytest-dev/pytest-bdd/pull/557>_.
• Make the package PEP 561-compatible [#559](https://github.com/pytest-dev/pytest-bdd/issues/559) <https://github.com/pytest-dev/pytest-bdd/issues/559>_ [#563](https://github.com/pytest-dev/pytest-bdd/issues/563) <https://github.com/pytest-dev/pytest-bdd/pull/563>_.
• Configuration option bdd_features_base_dir is interpreted as relative to the pytest 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/issues/573) <https://github.com/pytest-dev/pytest-bdd/pull/573>_

6.0.1

• Fix regression introduced in 6.0.0 where a step function decorated multiple using a parsers times would not be executed correctly. [#530](https://github.com/pytest-dev/pytest-bdd/issues/530) <https://github.com/pytest-dev/pytest-bdd/pull/530>_ [#528](https://github.com/pytest-dev/pytest-bdd/issues/528) <https://github.com/pytest-dev/pytest-bdd/issues/528>_

6.0.0

This release introduces breaking changes in order to be more in line with the official gherkin specification.

• Cleanup of the documentation and tests related to parametrization (elchupanebrej) [#469](https://github.com/pytest-dev/pytest-bdd/issues/469) <https://github.com/pytest-dev/pytest-bdd/pull/469>_
• Removed feature level examples for the gherkin compatibility (olegpidsadnyi) [#490](https://github.com/pytest-dev/pytest-bdd/issues/490) <https://github.com/pytest-dev/pytest-bdd/pull/490>_
• Removed vertical examples for the gherkin compatibility (olegpidsadnyi) [#492](https://github.com/pytest-dev/pytest-bdd/issues/492) <https://github.com/pytest-dev/pytest-bdd/pull/492>_
• Step arguments are no longer fixtures (olegpidsadnyi) [#493](https://github.com/pytest-dev/pytest-bdd/issues/493) <https://github.com/pytest-dev/pytest-bdd/pull/493>_
• Drop support of python 3.6, pytest 4 (elchupanebrej) [#495](https://github.com/pytest-dev/pytest-bdd/issues/495) <https://github.com/pytest-dev/pytest-bdd/pull/495>_ [#504](https://github.com/pytest-dev/pytest-bdd/issues/504) <https://github.com/pytest-dev/pytest-bdd/issues/504>_
• Step definitions can have "yield" statements again (4.0 release broke it). They will be executed as normal fixtures: code after the yield is executed during teardown of the test. (youtux) [#503](https://github.com/pytest-dev/pytest-bdd/issues/503) <https://github.com/pytest-dev/pytest-bdd/issues/503>_
• Scenario outlines unused example parameter validation is removed (olegpidsadnyi) [#499](https://github.com/pytest-dev/pytest-bdd/issues/499) <https://github.com/pytest-dev/pytest-bdd/pull/499>_
• Add type annotations (youtux) [#505](https://github.com/pytest-dev/pytest-bdd/issues/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/issues/505) <https://github.com/pytest-dev/pytest-bdd/pull/505>_
• Angular brackets in step definitions are only parsed in "Scenario Outline" (previously they were parsed also in normal "Scenario"s) (youtux) [#524](https://github.com/pytest-dev/pytest-bdd/issues/524) <https://github.com/pytest-dev/pytest-bdd/pull/524>_.

5.0.0

This release introduces breaking changes, please refer to the :ref:Migration from 4.x.x.

• Rewrite the logic to parse Examples for Scenario Outlines. Now the substitution of the examples is done during the parsing of Gherkin feature files. You won't need to define the steps twice like @given("there are <start> cucumbers") and @given(parsers.parse("there are {start} cucumbers")). The latter will be enough.
• Removed example_converters from scenario(...) signature. You should now use just the converters parameter for given, when, then.
• Removed --cucumberjson-expanded and --cucumber-json-expanded options. Now the JSON report is always expanded.
• Removed --gherkin-terminal-reporter-expanded option. Now the terminal report is always expanded.

4.1.0

... (truncated)

Commits

• 91e9623 bump version
• 4d44c88 Add regression test
• 34014cc Update changelog
• 7340cc1 call after scenario hook after all steps
• e5f2134 6.1.0 release
• 1d84d29 Revert "parsers.re now does fullmatch."
• b915c2a Merge pull request #576 from pytest-dev/ci-improvements
• 40a041f Let's start fixing DeprecationWarnings
• 3bbdbb3 disable spinner, otherwise the logs are just spam
• 922fab5 Merge remote-tracking branch 'origin/master' into ci-improvements
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)