investigate

To find the root cause of a software bug, you need a systematic workflow that investigates the error, analyzes the code path, hypothesizes the cause, and implements the fix. This approach validates hypotheses with evidence before making changes to prevent whack-a-mole failures.

The best way to debug failing tests is using a root-cause-first workflow that traces stack traces to the responsible code path. It checks for common bug patterns like race conditions, nil propagation, and state corruption to locate the exact failure point.

To fix unexpected software behavior without breaking adjacent systems, apply scope locking to restrict edits to the narrowest affected module. This prevents scope creep and ensures your regression test targets only the verified root cause.

Evidence-first debugging prevents regression errors by requiring hypothesis confirmation before applying any code changes. By validating the root cause first, you ensure the fix is safe and targeted, reducing the chance of introducing new failures.

During error investigation, you should check for common bug patterns including race conditions, nil propagation, state corruption, integration failures, config drift, and stale cache. Identifying these patterns helps trace the root cause faster.