022f1b4de5
Bumps [pytest-bdd](https://github.com/pytest-dev/pytest-bdd) from 7.0.0 to 7.0.1. - [Release notes](https://github.com/pytest-dev/pytest-bdd/releases) - [Changelog](https://github.com/pytest-dev/pytest-bdd/blob/master/CHANGES.rst) - [Commits](https://github.com/pytest-dev/pytest-bdd/compare/7.0.0...7.0.1) --- updated-dependencies: - dependency-name: pytest-bdd dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Bruno Oliveira <nicoddemus@gmail.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| README.rst | ||
| bdd_wallet.feature | ||
| bdd_wallet.py | ||
| django_settings.py | ||
| pytest.ini | ||
| pytest_anyio_integration.py | ||
| pytest_asyncio_integration.py | ||
| pytest_mock_integration.py | ||
| pytest_trio_integration.py | ||
| pytest_twisted_integration.py | ||
| requirements.txt | ||
| simple_integration.py | ||
README.rst
This folder contains tests and support files for smoke testing popular plugins against the current pytest version. The objective is to gauge if any intentional or unintentional changes in pytest break plugins. As a rule of thumb, we should add plugins here: 1. That are used at large. This might be subjective in some cases, but if answer is yes to the question: *if a new release of pytest causes pytest-X to break, will this break a ton of test suites out there?*. 2. That don't have large external dependencies: such as external services. Besides adding the plugin as dependency, we should also add a quick test which uses some minimal part of the plugin, a smoke test. Also consider reusing one of the existing tests if that's possible.