tdd

Enforce test-driven development by mandating the red-green-refactor workflow: write a failing test for the new behavior first, implement the minimal code to pass it, then refactor while maintaining pristine test output. This ensures validated, behavior-driven code and prevents regressions.

The red-green-refactor cycle in software engineering is a test-driven development workflow where you write a failing test, implement minimal code to make it pass, and then refactor the implementation while keeping tests green to ensure pristine test output.

Write effective tests that validate real behavior by focusing on minimal, behavior-driven assertions and using a red flag checklist to verify you are testing actual code execution rather than mock interactions, ensuring explicit test coverage for all new functionality.

You can use test-driven development for bug fixes by first writing a failing test that reproduces the specific bug, such as invalid empty email validation, then implementing the fix to pass that test, which prevents future regressions without disrupting your workflow.

You should not use test-driven development for throwaway prototypes and generated code, as these are pre-approved exceptions where strict workflow enforcement is bypassed to allow rapid iteration without requiring explicit test coverage.

If your test-driven development tests are difficult to write, use the provided troubleshooting tips to address common blockers, ensuring your tests remain focused on real behavior and follow the step-by-step instructions for each phase of the TDD cycle.