systematic-debugging

Root cause analysis for test failures requires gathering evidence and testing a single hypothesis minimally before implementation. You must complete four ordered phases, starting with investigation, to stop applying symptom patches that waste time and introduce new defects.

Debugging production incidents effectively means enforcing root cause investigation first. By completing pattern analysis and verifying implementation with tests or a clear validation step, you avoid quick patches that cause unexpected behavior across multi-component systems.

To stop fixing symptoms during incident response, follow a pressure-resistant workflow that mandates finding the root cause before any fixes. This method requires evidence gathering and single-hypothesis testing to prevent wasted time and new defects.

Root cause analysis applies to build failures, performance regressions, and flaky timing problems across single or multi-component systems. It enforces a four-phase debugging workflow to investigate technical failures thoroughly before you change code.

Testing a single hypothesis minimally during debugging isolates variables and confirms the root cause without introducing side effects. This disciplined approach prevents wasted effort on symptom patches and ensures implementation is verified by tests.

You should never use quick patches for technical failures or integration issues when you lack root cause investigation. Applying symptom patches without evidence gathering and hypothesis testing wastes time and risks introducing new defects into multi-component systems.