test-driven-development

To enforce test-driven development, write a failing test first, implement the minimal code required to pass it, and then refactor without introducing regressions. This RED-GREEN-REFACTOR cycle ensures deliberate, minimal implementations across Python projects.

The RED-GREEN-REFACTOR cycle is a test-driven development workflow requiring a failing test first, followed by minimal production code to pass it, and concluding with regression-free refactoring to ensure code quality.

To reduce regressions during refactoring, apply a test-first workflow by writing tests that act as living specifications before changing production code, ensuring minimal implementation and regression-free behavior.

Yes, test-first development applies to both bug fixes and feature development. It enforces writing a failing test before any production code, driving deliberate implementations and reducing regressions across the workflow.

You need to write a failing test before production code whenever you are developing features, fixing bugs, or refactoring. This ensures requirements are satisfied through a disciplined workflow and minimal implementation.