What problem does it solve? Python projects often accumulate inconsistent test suites with unclear naming, ad-hoc fixtures, and no coverage expectations. This Skill gives Claude a single, opinionated set of pytest conventions so every test file, fixture, and coverage check follows the same standard. ## Core Features & Use Cases - Test structure and naming: Enforces a tests/ directory layout where each test file mirrors its source file (test_ + source filename) and each test function covers one behavior. - Fixtures and parametrization: Provides conftest.py patterns, tmp_path/monkeypatch rules, parametrized test examples, and snapshot testing with syrupy. - Coverage thresholds: Sets an 80% line-coverage target with 100% public-function coverage, plus commands for running and reporting coverage via uv run pytest. - Use Case: Ask Claude to write tests for a new data-transformation module, and it will produce a properly named test file with parametrized cases, exception tests, and fixtures that match the project conventions. ## Quick Start Ask Claude to write pytest tests for a specific Python module following the project testing conventions.