bugfix-red-green-proof

A test-driven bug fix workflow prevents patchwork repairs by enforcing a red-green-proof loop. This five-step regression-driven process requires a failing regression test, a minimal root-cause fix, and re-running targeted and broader test suites to confirm green.

A red-green-proof loop for regression testing is a disciplined workflow that starts with a failing test, requires a minimal root-cause fix, and validates the change by re-running targeted and broader test suites to achieve green. This provides clear evidence and traceability of fixes.

Write a regression test for a software bug by reproducing the exact failure in a targeted test case. This failing test serves as the starting point for the bugfix loop, ensuring the minimal root-cause fix is validated and preventing future regressions.

You cannot use this regression-driven bugfix workflow without creating a test first. The process explicitly requires starting with a failing regression test to reproduce the failure before implementing the minimal root-cause fix and validating it across broader test suites.

Re-running broader test suites after a targeted bug fix guards against regressions. While the targeted test confirms the specific root-cause fix works, broader validation ensures the minimal change did not introduce new failures elsewhere in the software.