systematic-debugging

To find the root cause of test failures, you must enforce a systematic debugging workflow that completes evidence gathering and pattern analysis before proposing any code fixes. This prevents wasted time and new bugs.

Systematic debugging production defects requires a four-phase workflow: investigation, pattern analysis, single-hypothesis testing, and implementation. You must trace data flow and create a failing test before changing code.

To stop iterating on quick fixes during multi-component debugging, apply strict stop rules when multiple fixes fail. Gather evidence across component boundaries to locate the exact failure source instead of rationalizing shortcuts.

Creating a failing test before implementing a code fix ensures you have accurately reproduced the unexpected behavior and validated your root cause hypothesis. This prevents incorrect fixes and anti-flakiness in your system.

Systematic troubleshooting for build failures and integration problems requires strict adherence to evidence gathering and single-hypothesis testing. It limits rapid patching but prevents compounding new bugs across component boundaries.