a335ade1f5
* Rename pytest_ignore_collect fspath parameter to collection_path * Rename pytest_collect_file fspath parameter to file_path * Rename pytest_pycollect_makemodule fspath parameter to module_path * Rename pytest_report_header startpath parameter to start_path * Rename pytest_report_collectionfinish startpath parameter to start_path * Update docs with the renamed parameters * Use pytest-flakes fork temporarily to prove it works * Use pytest-flakes 4.0.5 |
||
|---|---|---|
| .. | ||
| .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.