test-driven-development

The red-green-refactor workflow in test-driven development requires writing a failing test first, implementing the minimal code to make it pass, and then safely refactoring the implementation while maintaining test coverage.

To fix bugs using test-first development, you write a failing test that reproduces the defect, implement the minimal code change to make the test pass, and refactor the software to ensure reliable automated verification.

You should apply test-driven development when adding new features, fixing defects, or changing behavior to ensure the resulting code is covered by meaningful automated tests and avoids common testing anti-patterns.

Common testing anti-patterns avoided during refactoring include writing implementation code before tests, skipping test validation steps, and building implementations that exceed the minimal code needed to pass the failing test.

Yes, test-driven development enforces automated test verification for behavior changes by requiring tests to fail for the right reasons before implementation and confirming they pass after the minimal code is written.