bug-fix-protocol

Fix a production bug by pairing a minimal code correction with a targeted test-system improvement. Generate a failing test reproducing the defect, apply the smallest root-cause fix, verify locally, and audit coverage gaps to prevent recurrence.

The best way to write a failing test for a regression is using a test-first repair workflow. Create a red test reproducing the exact defect across unit or integration layers before implementing the minimal code change to turn it green.

A post-mortem testing-system audit is needed because customer-reported defects reveal quality-net blind spots. Diagnosing why coverage missed the issue and prescribing concrete improvements ensures the testing system catches similar regressions next time.

Trace a regression to its smallest root-cause change by reproducing the defect with a failing test, then analyzing the code path to isolate the exact minimal modification required to resolve the symptom and restore expected behavior.

Yes, you can use this bug fixing protocol for both unit and integration test gaps. It applies to regressions, customer-reported defects, post-mortems, and explicit test-gap investigations across both testing layers to ensure comprehensive coverage.

Avoid a test-first repair workflow when a production bug cannot be reliably reproduced in a test environment, or when the defect stems from external infrastructure failures rather than actionable code-level root causes within your system.