tdd

Automate test-driven development by planning a tracer bullet, writing a failing test, implementing minimal code to pass, and refactoring with dependency-injected interfaces. This enforces structured red-green-refactor cycles to ensure behavior is verified through public interfaces.

Structure red-green-refactor cycles by progressing one test at a time from a failing test to minimal implementation to passing tests. This behavior-focused approach emphasizes integration-style tests over internal implementation details to reduce brittle refactors.

Use tracer bullets in test-driven development when you need to plan and verify an end-to-end vertical slice of a feature. Tracer bullets establish the initial failing test and minimal implementation path before applying full red-green-refactor loops.

Yes, test-driven development workflows apply to both building features and fixing bugs. You write a failing test that reproduces the bug or defines the new behavior, then implement just enough code to make the test pass before refactoring.

Refactoring in TDD requires dependency-injected interfaces to verify behavior through public interfaces without relying on internal implementation details. This disciplined refactoring approach reduces miscommunication and prevents brittle code during incremental development loops.

Start a TDD loop by planning the first tracer bullet and writing a single failing test. Implement just enough code to pass that test, ensuring incremental, behavior-focused progression before performing any structural refactoring.