Skip to main content
Strategy & Process
DEFINITION

What is Defect Leakage?

Defect leakage (also called defect escape) measures the share of defects that were missed in testing and found later, in a higher test phase or in production, indicating how effective the earlier testing was. It is calculated as defects found after a phase divided by total defects, and a rising rate is the clearest signal that coverage has fallen behind.

No account needed · Scored in under a minute against a senior rubric

IN DEPTH

What does Defect Leakage mean in practice?

Defect leakage answers a sharper question than "how many bugs did we find?": "how many did we miss?" A common formula is defects found after a phase divided by total defects (found in the phase plus those that escaped), often expressed as a percentage. The most-watched version is production escape: defects found by users divided by all defects for that release.

It is one of the best signals of test effectiveness. Rising leakage means tests are not catching what they should, perhaps a coverage gap, weak environments, or rushed cycles. Falling leakage, paired with stable or rising defect detection, means testing is genuinely getting better, not just running more.

The interview nuance is interpretation. Like all metrics it can be gamed (classify escapes as "enhancements") and must be read in context, a tiny absolute number can produce a scary percentage. It pairs naturally with defect density and detection effectiveness for a fuller picture, and a healthy team uses each escaped defect as a root-cause-analysis prompt, not a blame tool.

WHY IT MATTERS

Why do interviewers ask about Defect Leakage?

For lead and quality-engineering interviews, defect leakage shows you can measure whether testing actually works, not just activity. Tying escapes to root cause analysis and prevention is the strongest possible framing.

EXAMPLE

What does Defect Leakage look like in a real project?

A release finds 90 defects in testing and users report 10 in production. Leakage is 10 / 100 = 10%. RCA on the 10 escapes shows most were on mobile Safari, an untested environment, so the team adds it to the matrix and leakage drops the next release.

TIP

How should you talk about Defect Leakage in an interview?

Give the formula (escaped defects over total), distinguish it from defect density (which counts defects per size, not misses), and tie escapes to root cause analysis. That progression, measure then prevent, is the signal.

FAQ

Common questions about Defect Leakage

What is the difference between defect leakage and defect density?

Defect leakage measures the proportion of defects missed in testing and found later (test effectiveness). Defect density measures defects per size unit such as per KLOC (where defects cluster). One is about misses, the other about concentration.

What is a good defect leakage rate?

Lower is better, but the right target depends on the product and risk. The useful signal is the trend over releases and whether escapes are being root-caused and prevented, not a single universal number.

FREE TOOLS  /  no signup

Free QA career tools, no account needed

Instant and private, everything runs in your browser. Try them before you sign up.

EXEC.NOW

Ready to Ace Your QA Interview?

Practice explaining defect leakage and other key concepts with our AI interviewer.

Join 500+ QA engineers already practicing with AssertHired.

Question 1 · Automation · Mid-levellive scoring

A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.

Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.

Rather skip ahead? Create a free account

FREE.TO.START  ·  7.DAY.TRIAL ON PAID PLANS
Written by , Senior QA Automation Engineer, 50+ QA candidate interviews conductedLast updated July 2026