build(deps): Bump pytest-bdd from 5.0.0 to 6.0.1 in /testing/plugins_integration

[dependabot]

Bumps pytest-bdd from 5.0.0 to 6.0.1.

Release notes

Sourced from pytest-bdd's releases.

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.

Changelog

Sourced from pytest-bdd's changelog.

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>_.

Commits

• 7393b46 Merge pull request #530 from pytest-dev/fix-parsed-step-aliases
• 533b5cd Bump version, update changelog
• 15e1a8a Handle multiple parsers connected to a step function
• 81a9264 Merge pull request #529 from pytest-dev/changelog-6.0.0
• 658c202 Update changelog for 6.0.0 release
• 55e43da Merge pull request #518 from pytest-dev/pre-commit-ci-update-config
• 2411ac2 Merge branch 'master' into pre-commit-ci-update-config
• 2ae7d33 Merge pull request #526 from pytest-dev/update-readme
• 0cd4d14 Fix filename
• a9bbf89 Fix copy
• 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)