arc-tdd

To implement test-driven development, enforce a strict red-green-refactor cycle by writing a failing test first, writing minimal code to pass, and refactoring afterward to ensure code quality and prevent regressions.

The red-green-refactor cycle in TDD is a development workflow where you write a failing test, write the minimal code required to make that test pass, and then clean up the implementation without breaking functionality.

To avoid common testing anti-patterns when writing tests first, follow strict TDD principles that prevent rationalizations for skipping tests and guide you away from pitfalls that cause code regressions and quality degradation.

Yes, you can use test-driven development for both new features and bug fixing by enforcing the red-green-refactor cycle across all development workflows to prevent regressions and ensure code meets requirements before implementation.

You should write failing tests before implementation code because it defines expected behavior upfront, ensures code is robust, meets requirements, and prevents bugs and regressions throughout the development workflow.