tdd-pytest

Test-driven development with pytest starts by writing failing tests first, then implementing code to pass them using the Red-Green-Refactor cycle. Configure pytest in pyproject.toml, organize tests with fixtures and parametrization, then run tests with coverage reporting to validate your implementation.

Yes, pytest with coverage generates detailed reports of code paths tested. This Skill automates running tests with coverage, producing TESTING_REPORT.local.md to document test results and coverage metrics configured in pyproject.toml.

Organize pytest fixtures by scope and reusability, apply parametrization for multiple test cases, and follow framework-appropriate patterns for async and exception testing. This Skill provides templates and examples for structuring tests that follow pytest best practices.

Auditing pytest files involves reviewing test organization, fixture usage, coverage gaps, and adherence to TDD principles. This Skill analyzes existing pytest configurations and test structure to identify quality issues and suggest improvements aligned with Red-Green-Refactor workflows.

While pytest runs independently, using uv with pyproject.toml simplifies dependency management and test execution. This Skill configures both to streamline running pytest commands and managing test coverage as part of a unified Python project setup.

Test-driven development ensures code meets requirements from the start, improves design clarity, and catches bugs early. The Red-Green-Refactor cycle—writing failing tests, implementing code, then refactoring—produces more maintainable and reliable Python applications.