fixing-bugs

To fix a bug using a regression test, you first reproduce the failing behavior with a targeted test, implement a minimal root-cause fix, and verify the full test suite succeeds before committing. This prevents symptom patching and recurrence.

The failing-test-first methodology for debugging requires writing a regression test or minimal reproduction that captures the bug before changing any code. This ensures the divergence point is reliably located and guarded against future regressions.

You verify a bug fix by running targeted regression tests using pytest or jest, then executing a verification script. This validates that the minimal root-cause fix resolves the failure without introducing new regressions.

Yes, you can use this test-driven debugging workflow for script regressions. It applies to debugging tasks for unit, integration, or script regressions where a failing-test-first approach and environment reproductions are feasible.

The best way to ensure a minimal root-cause fix for a unit test failure is to use targeted reading and grepping to locate the divergence point, apply the smallest possible code change, and validate against the full test suite.

You need a verification script before committing bug fixes to satisfy pre-commit gates and validate that the targeted regression tests pass. This ensures the fix is fully validated before handing off to the repository commit workflow.