dev-style-tdd

The red-green-refactor cycle in test-driven development is an iterative process where you write a failing test, implement the minimal code to pass it, and then refactor while preserving behavior to reduce rework and brittleness.

To execute a tracer bullet cycle for feature development, write one failing integration test that exercises a public interface, implement the minimal code required to pass it, and then refactor the implementation iteratively.

You should write integration tests for public interfaces rather than internal implementations to express intended behavior and ensure observable outcomes, which reduces brittle refactors during test-driven development.

Test-driven development works for both feature development and bug fixes by guiding teams to express intended behavior through public interfaces using incremental vertical slices and disciplined refactoring.

Emphasizing implementation details causes brittle refactors because tests become tightly coupled to internal code structures rather than observable outcomes, increasing rework when the underlying implementation changes.

You can apply test-driven development to any software project without specific framework dependencies, as the process focuses on expressing behavior through public interfaces using vertical slices and integration tests.