QA Debugging (Jan 2026)

Use systematic debugging to turn symptoms into evidence, then into a verified fix with a regression test and prevention plan.

Quick Start

Intake (Ask First)

• Capture the failure signature: error message, stack trace, request ID/trace ID, timestamp, build SHA, environment, affected user/tenant.
• Confirm expected vs actual behavior, plus the smallest reliable reproduction steps (or “cannot reproduce” explicitly).
• Ask “when did this start?” and “what changed?” (deploy, flag, config, data, dependency, infra).
• Identify blast radius and urgency: who/what is impacted, and whether this is an incident.

Output Shape (Default)