diagnosing-test-failures
Diagnoses a failing test or a reported defect to its root cause: classifies the failure (application defect, test bug, environment or config, flaky, or test data), builds a tight reproduction loop that goes red on the exact symptom, tests ranked falsifiable hypotheses one variable at a time, and resolves it by class without weakening assertions. Use when a test fails on every run or since a merge, a CI job is red, someone asks "why is this failing", a bug is reported and needs a root cause, or a stack trace, error log, or trace file is pasted, even if the word debug is never used. When the failure is intermittent, hand over to stabilizing-flaky-tests; when the cause is an application defect, write it up with reporting-bugs.
Pinned to revision c4efc46815a7, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/diagnosing-test-failures/SKILL.md
- skills/diagnosing-test-failures/resources/ci-only-failures.md
- skills/diagnosing-test-failures/resources/classification-evidence.md
- skills/diagnosing-test-failures/resources/diagnosis-record.md
- skills/diagnosing-test-failures/resources/feedback-loops.md
Every link opens the file at its source, pinned to the revision this page describes.