gezel Gezel Handboek

Reproduce-Then-Fix a Bug

Fix a bug the disciplined way: first write a failing test that reproduces it, then make the smallest change that turns the test green without breaking others, then verify and guard against regression. Reproduces FIRST with a red test that captures the exact wrong behavior — because a bug you cannot reproduce you cannot prove fixed — then applies the minimal fix, then a reviewer confirms the new test passes, root cause is addressed, and the suite is green. Covers test-driven bug fixing, regression tests, minimal diffs, root-cause vs symptom, and red-green verification.

How it runs

#StepWho runs itWhat happens
1Reproduce with a failing testDeveloperwrite a red test that captures the wrong behavior
2Apply the minimal fixDevelopersmallest change that turns the test green
3Verify the fixReviewerconfirm green, root cause fixed, no regressions
4EvaluateReviewerGrade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
5FinishDeveloperAll acceptance criteria met. Stamp a short summary and report DONE.

Say something like "fix this bug" or "reproduce and fix" or "tdd bug fix" or "write a regression test" or "debug and fix" in chat to start it.

Watch this article as a slideshow