ad-tdd

A TDD workflow enforces behavior testing by driving features through red-green-refactor cycles using one public-interface test at a time, preventing implementation-driven testing and horizontal slicing. This ensures tests express observable behavior.

The red-green-refactor cycle is a TDD process that advances features incrementally using one test at a time. It prevents horizontal slicing by enforcing vertical planning and testing observable behavior via public interfaces, maintaining a fast feedback loop.

Yes, you can drive a feature from red to green using a tracer bullet approach. The workflow includes a tracer bullet phase followed by an incremental loop, allowing you to establish end-to-end behavior before iterating with individual tests.

TDD guardrails are designed for typical software components with behavior-known interfaces. The workflow applies to these scopes by enforcing that tests express observable behavior and maintaining a fast green/red feedback loop.

The best way to maintain a fast feedback loop in TDD is to use a five-phase workflow: confirm regime, plan vertically, tracer bullet, incremental loop, and refactor while green. This structure ensures one-test-at-a-time cycles with explicit decision points.

You should refactor during the TDD workflow only while your tests are green. The workflow includes a dedicated refactor phase that occurs after the incremental loop, ensuring you improve code structure safely without changing observable behavior.