systematic-debugging

To find the root cause of a failing test, use a systematic debugging process that enforces reproducible investigation steps, pattern analysis, and hypothesis testing before applying any code fixes. This prevents symptom-only patches.

The best way to debug production errors is enforcing a root-cause-first workflow with hypothesis testing and validation. This systematic investigation ensures you fix the underlying issue rather than applying temporary symptom patches.

Investigate flaky tests systematically by following a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation with validation, explicitly avoiding multiple-change attempts or shortcut fixes.

Yes, you can use systematic debugging for performance regressions and unexpected behavior. It mandates reproducible investigation steps and hypothesis testing to guide error investigation and ensure reliable fixes across any code breakage scenario.

Bug fixes cause new errors when developers skip investigation and apply symptom patches. Systematic debugging prevents this by enforcing a disciplined root-cause-first workflow with anti-pattern safeguards against shortcut fixes and multiple-change attempts.

You should not avoid systematic debugging for error investigation, but note it mandates a four-phase process. If you need an immediate shortcut fix without hypothesis testing or validation, this root-cause investigation workflow will intentionally block rapid patches.