test-driven-development

Test-driven development fixes bugs by writing a failing test that reproduces the issue first, then implementing the minimal code to pass it. This validates behavior and prevents regressions during bug fixes.

The red-green-refactor cycle is a unit testing workflow where you write a failing test, implement the minimal solution to pass it, and then refactor the code while keeping tests green to ensure quality.

Start writing failing tests by defining expected behavior for a new feature before any implementation. Run the test to confirm failure, then write the minimal code needed to pass it.

Test-driven development works for refactoring codebases by validating expected behavior with tests before changes. You keep tests green while restructuring code to ensure correctness throughout the refactor.

Avoiding mocking anti-patterns in TDD ensures tests validate actual behavior rather than implementation details. Proper mocking maintains test reliability and prevents false positives during the red-green-refactor cycle.

Test-driven development may not suit exploratory programming or throwaway prototypes where behavior is undefined. It requires clear, verifiable requirements to drive implementation and validate correctness effectively.