tdd-workflow

Test-driven development is enforced by requiring a failing test to be written and confirmed before any implementation code is written. This workflow drives features and bug fixes through the Red-Green-Refactor cycle to prevent shipping untested code.

The Red-Green-Refactor cycle is a test-driven development workflow where you write a failing test, implement the minimal code required to make that test pass, and then clean up the code while keeping the full test suite green.

Pre-commit hooks block implementation-only commits by enforcing test-driven development checks and CI coverage requirements before code is merged. These guardrails ensure automated checks specify features and stop fragile implementation code from being shipped.

Test-driven development workflows should be used when refactoring untested legacy code to add safety nets, reproducing and fixing bugs with regression tests, starting new features, and integrating changes into CI and pre-commit checks.

A configured test framework runnable from the command line is required to run test-driven development workflows. This independent test execution environment supports guardrails like coverage thresholds and pre-commit hooks.

Writing failing tests first prevents shipping fragile implementation code by ensuring features and bug fixes are specified by automated checks before the implementation is written. This test-driven approach guarantees code is validated immediately.