test-driven-development

The red-green-refactor cycle in test-driven development means writing a failing test first, implementing the minimal code to pass it, then refactoring while keeping tests green. It prevents regressions and guides design decisions.

To write a failing test before implementation, capture the intended behavior in a unit test that initially fails. Then, implement just enough minimal production code to satisfy requirements and make the test pass.

Yes, you can apply test-driven development to bug fixes and refactoring workflows. Writing tests first prevents regressions and validates code changes before implementation, ensuring reliable software engineering outcomes.

Test-driven development reduces debugging time and code drift by validating code with tests before implementation. This structured approach pushes development through failing tests, ensuring explicit test suites satisfy requirements.

No specific testing framework is required. Test-first development relies on the principle of maintaining an explicit test suite and prioritizing minimal production code, which can be applied across any software engineering environment.

You should avoid test-driven development when validating exploratory prototypes where requirements are unknown, as the cycle requires writing explicit tests that capture intended behavior before any production code exists.