Understanding Defect Rejection Rate
How we calculate. Rejection % = (rejected ÷ reported) × 100. The form uses the same arithmetic as the worked examples on this page. See our methodology and accuracy policy.
Real-world scenario: A typical Defect Rejection Rate case uses rejected defects 15 and total reported defects 100. Enter the same figures below to reproduce the worked path.
What is Defect Rejection Rate?
This QA/process metric measures report quality and triage efficiency. It is not a product quality score by itself.
- Includes: invalid, duplicate, cannot reproduce, works as designed (per your taxonomy)
- High rate: may mean tester training gaps or ambiguous specs
- Very low rate: can mean weak triage (accepting noise as bugs)
The Formula
Worked Example
Common Use Cases
- Triage health: monitor noise in the defect funnel
- Training: coach teams with chronic invalid reports
- Dev/QA partnership: clarify “works as designed” boundaries
Pro Tips
- Separate duplicates from invalid in deeper reports
- Do not punish filing — improve clarity of expected behavior
- Track by reporter role (manual QA vs automation vs support)
Limitations: Defect Rejection Rate results are estimates for learning and QA planning—not contractual SLAs. Align definitions with your org’s quality glossary before executive reporting.
FAQ
Are deferred defects rejected?
No. Deferred/postponed items are usually valid defects scheduled later—keep them out of the rejection numerator.
What is a healthy rejection rate?
It varies. Many teams watch for sudden spikes more than a fixed universal target.
Authoritative References
For software quality metrics definitions, consult established engineering sources:
- ISTQB — software testing glossary and practices
- ISO/IEC 25010 — systems and software quality models
- IEEE — software engineering standards