test-driven-development

Test-driven development uses the red-green-refactor cycle: write a failing test, implement minimal production code to pass it, and refactor while keeping tests green. This workflow enforces testing discipline and prevents unnoticed regressions during feature development.

Enforce test-driven development by requiring a failing test before any production code. Implement minimal code to pass the test, then refactor. This guardrail prevents untested features and guides correct behavior across refactors and behavior changes.

Writing a failing test before production code ensures the test actually validates the new behavior. This test-driven approach prevents unnoticed regressions, documents expected behavior, and guides disciplined feature development from the start.

Test-driven development applies to refactoring by keeping all existing tests green while you clean up the code. The red-green-refactor cycle ensures behavior remains unchanged during structural improvements and behavior changes.

Test-driven development applies to both new features and bugfix work. Write a failing test that captures the desired behavior or bug scenario, implement minimal code to pass it, and refactor with confidence that tests prevent regressions.