tdd

To enforce test-driven development in Python, this skill guides you through the red-green-refactor workflow, ensuring you write failing tests first and implement just enough code to pass them using pytest.

The contracts-first workflow for test-driven development defines a strict sequence: contract → models → tests → implementation, reducing defects by establishing boundaries and validating models before writing the actual application logic.

Yes, you can use pytest fixtures and mocks when following a test-first workflow, as this skill provides specific templates and patterns for common test cases including setup fixtures and mocks to isolate dependencies.

The best way to start writing tests before implementation is to write a failing test for a new feature, then run pytest with coverage to verify the failure before writing the minimal code required to pass it.

You should not use the red-green-refactor workflow in isolation if your project lacks model validation steps, as this skill specifically relies on a defined sequence of contract definition and model validation to reduce defects.

Yes, test-driven development works for bug fixes in Python projects by guiding you to write a failing test that reproduces the bug first, then modifying the implementation until the test passes within the red-green-refactor cycle.