test-driven-development

Test-driven development enforces a Red-Green-Refactor cycle: write a failing test, implement minimal production code to pass it, then refactor for clarity with validation guardrails to prevent regression.

Yes, test-driven development applies to bug fixes and refactoring by ensuring tests guide behavior across changes, enforcing a test-first workflow to improve reliability and maintainability.

The Red-Green-Refactor cycle in unit testing involves writing a failing test, implementing minimal production code to pass, and refactoring with guardrails and validation to prevent scope creep.

Writing tests before production code improves code quality because test-driven development enforces a disciplined test-first workflow, ensuring tests guide behavior and preventing production bugs from slipping in.

No specific frameworks are required. The test-first workflow relies on explicit steps, checks, and documentation to enforce discipline, rather than depending on external testing frameworks.

You should avoid test-driven development when exploring experimental code where behavior is undefined, as the test-first workflow requires explicit behavior expectations to write failing tests initially.