systematic-debugging

Root cause analysis for debugging requires gathering diagnostic data like logs and traces to locate the source of a bug before proposing any fixes. A structured workflow enforces investigation through pattern analysis, hypothesis testing, and verification.

Systematic debugging of unit, integration, and end-to-end tests uses a structured workflow: build a fast reproduction, investigate root causes, analyze patterns, test hypotheses, and implement fixes with a failing test case to verify the resolution.

Create a fast, red-capable reproduction command that isolates the exact user-facing symptom and surfaces the root cause. This initial feedback loop exposes the specific failure before you proceed to deeper diagnostic investigation.

Systematic debugging applies to diagnosing bugs across unit, integration, and end-to-end issues, including tests, APIs, and UI bugs. It enforces a consistent root-cause investigation workflow regardless of the specific software layer.

Root-cause analysis involves gathering diagnostic data to find the source, comparing against known-good patterns to identify diffs, forming a single testable hypothesis, applying a focused fix, and verifying across the system with a failing test case.

Pattern analysis during debugging compares the failing system against references and known-good patterns to identify diffs. This step isolates the specific divergence causing the failure before you form a testable hypothesis or implement a fix.