← ClaudeAtlas

defect-escape-taxonomylisted

Use when a defect has been confirmed in production and the team must name which class of gap let it through before deciding what to build. Classifies it as a test, process or tooling gap and one of thirteen sub-patterns at the earliest layer that should have caught it, with the fix, without blame.
testland/qa · ★ 13 · Testing & QA · score 80
Install: claude install-skill testland/qa
# defect-escape-taxonomy ## What this classifies A defect is "an imperfection or deficiency in a work product where it does not meet its requirements or specifications or impairs its intended use" ([ISTQB, defect](https://glossary.istqb.org/en_US/term/defect)). When a defect reaches production, the interesting question is not what the defect was. It is which checking activity was supposed to stop it and did not. ISTQB has a formal term for exactly this: an **escaped defect** is "a defect that is not detected by a test activity that is supposed to find it" ([ISTQB, escaped defect](https://glossary.istqb.org/en_US/term/escaped-defect)). That definition is the whole skill in one sentence. Classification means naming the test activity that was supposed to find it, then naming why that activity did not. The three categories and thirteen sub-patterns below are a **practitioner taxonomy**, not a standard. ISTQB and ISO/IEC/IEEE 29119 define the vocabulary (defect, escaped defect, root cause, quality gate) but neither publishes this three-way split. Treat the categories as a working classification your team can amend, and treat the cited definitions as fixed. The output of this classification is a **root cause** in the ISTQB sense: "a source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed" ([ISTQB, root cause](https://glossary.istqb.org/en_US/term/root-cause)). Note "the defect type", not "the defect". A correct classification is