incremental-tdd

To stop writing multiple tests upfront in TDD, you enforce a strict incremental cycle of writing one failing test, making it pass, and refactoring. This actively counters rationalizations for batch testing that undermine incremental design discovery.

Integrating ADR compliance during code refactoring involves evaluating your code quality against Architecture Decision Records immediately after the Green phase. This ensures your incremental design adjustments align with established architectural decisions before proceeding to the next test.

Writing multiple tests at once defeats Test-Driven Development because it skips the incremental design discovery process. Batch testing prevents you from evaluating and evolving the architecture after each individual test passes, locking in premature design choices.

Following the Red Green Refactor cycle strictly requires writing one failing test, implementing the minimum code to make it pass, and then refactoring with ADR compliance checks. This disciplined repetition prevents common rationalizations that defeat incremental TDD.

You should evaluate architectural decisions during the Refactor phase of the TDD process. After making a single failing test pass, incorporate Architecture Decision Record compliance checks to ensure your code quality and design meet established guidelines.