CodeVetter · Repo Unpack · Contributor handoff
pytest-dev/pytest
Tests and CI were inspected, not executed, and the investigation is bounded rather than exhaustive. Future changes should begin with the public API, configuration lifecycle, and the specific plugin module involved. Lifecycle cleanup, configuration precedence, worker conditions, and downstream plugin compatibility are concrete review boundaries. Execution commands below are repository-documented follow-up checks for an authorized implementation session, not results from this investigation.
- Read pyproject.toml, tox.ini, pytest/__init__.py, and pytest/__main__.py first to establish package requirements, test commands, public exports, and the actual CLI entrypoint.
- For startup changes, read Config.parse and findpaths together: parsing stages combine options and load plugins, while loader ordering determines which configuration wins and which files are reported as ignored.
- For execution changes, preserve teardown after setup failure, request/funcargs cleanup in finally, sessionfinish gating, and final unconfiguration; these are separate cleanup obligations.
- For fixture changes, inspect dependency loading before cache checks and finish() invalidation; targeted tests include testing/python/fixtures.py cases for scoped reuse and cached setup exceptions.
- For cache or reporting changes, retain path containment and worker suppression, and inspect matching test assertions rather than assuming they passed; relevant targets include test_cacheprovider.py, test_runner.py, and test_terminal.py.
- CONTRIBUTING.rst documents tox -e py312 -- testing/test_config.py and direct pytest testing/test_config.py after development setup; tox -e linting runs configured pre-commit checks, including Ruff and mypy.
- Do not equate default suite inspection with integration coverage: plugin examples are excluded from discovery, tox runs integrations separately with BDD disabled, and selected CI matrix jobs allow failure.
- Compatibility traps include deprecated console_main, native rejection of unhandled async tests and fixtures, and deprecated nodeid fixture registration; documented behavior changes normally require an issue-numbered typed changelog fragment.