What is Defect Removal Efficiency (DRE)?

Defect removal efficiency (DRE) is a quality metric that measures the percentage of defects a team finds and removes before release, calculated as defects found before release divided by total defects (those found before release plus those found by users afterward), times 100.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

DRE answers "how good is our testing at catching defects before customers do?" The formula is: DRE = (defects found before release) / (defects found before release + defects found after release) x 100. If testing finds 90 defects and users later report 10, DRE is 90 / 100 = 90%. A higher DRE means the team is catching more issues internally; 100% would mean no defect escaped to users.

It is a lagging, outcome metric, you can only finalize it once post-release defects accumulate, so it is typically computed per release or period and tracked as a trend. Rising DRE suggests improving test effectiveness; falling DRE signals escapes that warrant investigation (gaps in coverage, rushed testing, environment differences).

Like all metrics, DRE can be gamed or misread: it depends on accurately counting and attributing defects, and a team could look good simply because users have not yet found the escaped bugs. It is most useful as a trend alongside other signals (escaped-defect severity, coverage, lead time), not as a single target. Used well, it focuses attention on shifting defect discovery earlier, the economic heart of good QA.

WHY IT MATTERS

Why interviewers ask about this.

DRE is a common QA metrics interview topic, especially for lead and manager roles. Knowing the formula and, more importantly, its limitations (lagging, gameable, attribution-dependent) shows you can use quality metrics thoughtfully rather than chasing a number.

EXAMPLE

Example scenario.

For a release, the team logs 180 defects found in testing and, over the following weeks, 20 defects reported by users. DRE is 180 / (180 + 20) = 90%. Tracking it across releases, a drop to 75% on the next release prompts the team to investigate a coverage gap in a newly added module.

TIP

Interview tip.

State the DRE formula, defects found before release over total defects (before plus after) times 100, and interpret it as test effectiveness at catching issues before users. Then add nuance: it is a lagging, trend metric that can be gamed and depends on accurate defect attribution, so use it alongside other signals.

FAQ

Frequently asked questions.

How do you calculate defect removal efficiency?

DRE = (defects found before release) / (defects found before release + defects found after release) x 100. For example, 90 defects found in testing and 10 found by users gives 90 / 100 = 90%. Higher is better; it reflects how many defects the team caught internally versus letting escape to users.

What are the limitations of DRE?

It is a lagging metric (you need post-release defects to finalize it), depends on accurately counting and attributing defects, and can mislead if escaped bugs simply have not been found yet. It is best used as a trend alongside other signals, severity of escapes, coverage, lead time, not as a single target to chase.