systematic-debugging

Root cause debugging enforces a phase-based workflow starting with explicit diagnostics and pattern analysis to uncover the true source of flaky integration failures before applying fixes.

Systematic debugging uses a four-phase workflow requiring explicit diagnostics and canonical owners to reliably resolve unit test failures under time pressure without symptom-only patches.

Prevent regressions by applying defense-in-depth validations and quality gate checks during the implementation phase to ensure robust repairs and dual-track closure of complex bugs.

Yes, phase-based debugging applies to unit tests, integration failures, and flaky behavior by enforcing hypothesis testing and pattern analysis across all testing scopes.

Symptom-only patches cause new issues because they skip root cause investigation; applying a phase-driven workflow with canonical owners ensures the actual source is fixed.

Avoid symptom fixes whenever dealing with flaky behavior or integration failures, and instead require explicit diagnostics and pattern analysis to identify the root cause first.