test-driven-development

The test-driven development workflow prevents regressions by requiring a failing test before writing production code, ensuring automated tests validate all changes and enforce strict quality guardrails.

To apply red-green-refactor for bug fixes, you write a failing test that reproduces the bug, implement the minimum production code to pass the test, and then refactor safely while keeping tests green.

You need to write a failing test before writing production code whenever you are doing feature work, bug fixes, or refactoring to ensure you only implement minimal code required to pass the test.

Test-driven development works for safe refactoring by providing quality guardrails that document expected behavior, allowing you to modify code with confidence while keeping tests green throughout the process.

The best way to ensure minimal production code during feature work is to follow a strict red-green-refactor cycle, writing tests that cover behavior and implementing only enough code to pass them.