Pytest Deprecation Lint (pytest 8 removals)

It reads a test file, conftest.py, pytest.ini, pyproject.toml, setup.cfg or tox.ini and flags each line that current pytest handles differently than it reads: APIs removed in pytest 4.0 through 8.0, and config tables pytest ignores. Every finding names the removal version and prints the replacement line.

Python developers and QA engineers holding a pytest suite that predates the pytest 8 bump, and anyone reviewing test code an assistant generated. Assistants were trained on years of pytest 6 and 7 examples, so yield_fixture, pytest.warns(None) and message= keep reappearing in new files.

Ruff, flake8 and pylint check Python, not pytest's own removal history or its config tables. None of them tells you that a [tool.pytest] table in pyproject.toml is being ignored, that a mark above a fixture does nothing, or that parametrize on a TestCase subclass never injects its arguments.

Linting the file you have open is free and complete: all 19 rules, every finding, every replacement line, no key and no account. The paid tier adds a different job, not a bigger one: sweeping the whole workspace in one pass and exporting dated findings as Markdown or JSON you keep.

Reading a mid-sized suite line by line against the pytest changelog is an afternoon for someone who knows pytest, and a contract Python engineer in the US market bills roughly $80 to $120 an hour for it. The extension is $29 once, with a 7-day full refund.