Defect metrics, when used carefully, provide a window into where and when problems are discovered. Instead of using them for blame, effective teams use defect and escape rates to refine their testing strategy and engineering practices.
Working with Defect Counts and Escape Rates
Defect metrics often track the number of issues found per phase, their severity and which ones escape into later environments or production. Escape rate typically measures how many serious issues are found after release compared to before.
Example defect metrics:
- Total defects per release, grouped by severity
- Escaped defects: issues reported from production after release
- Phase found: requirements, development, system test, production
- Defect density: defects per KLOC or per story (used carefully)Used in a learning culture, escape rates highlight opportunities to shift tests earlier or improve critical path coverage.
Common Mistakes
Mistake 1 — Focusing only on the number of bugs found
This misses context.
❌ Wrong: Treating more bugs as always bad or always good.
✅ Correct: Look at severity, escape rate and root causes.
Mistake 2 — Ignoring production feedback
This hides reality.
❌ Wrong: Measuring only pre-release defects and ignoring what users experience.
✅ Correct: Track escaped defects and incorporate them into planning and testing.