Free QA Metrics Calculator
The numbers every test status report needs: execution rate, pass rate, defect density, and defect removal efficiency - calculated live, interpreted honestly, and exportable as a summary you can paste into the release meeting.
Test execution progress
How far along the cycle is, and how healthy the results are.
Defect density
Defects found relative to the size of what was tested.
Defect removal efficiency (DRE)
How many defects your process caught before they reached users.
QA Metrics Summary
Enter numbers on the left - the summary builds itself as you type.
How it works
Enter your cycle numbers
Planned and executed test cases with pass/fail/blocked counts, defects found against the size of what you tested, and defects caught before versus after release.
Read the computed metrics
Execution and pass rates, defect density per KLOC / story / requirement, DRE and leakage - each with an interpretation, not just a number.
Export the summary
A clean one-page summary as PDF, Word, or Markdown - ready for the status report or the release go/no-go meeting.
What these metrics actually tell you
Execution rate answers "are we on schedule?"; pass rate answers "is the build healthy?". They move independently - 95% executed with a 70% pass rate is a very different release conversation than 60% executed with 98% passing. Reporting them together is what makes a status report useful.
Defect density normalizes bug counts by size, which is what makes numbers comparable: 24 defects in a two-screen feature and 24 defects across an entire release are not the same signal. Pick the size unit your team already uses - KLOC, function points, stories, or requirements - and stay consistent.
Defect removal efficiency (DRE) is the retrospective metric: of all the defects that existed, how many did your process catch before users found them? Above 95% is strong, 85-95% is typical, and below 85% means testing is leaking - usually a coverage problem, not an effort problem.
Frequently asked questions
Is this QA metrics calculator free?
Yes - free, no signup, no limits. Everything is calculated in your browser; none of your numbers are uploaded anywhere. It is built by the team behind BesTest, a test management app for Jira.
How is defect removal efficiency (DRE) calculated?
DRE = defects found before release / (defects found before release + defects found in production), expressed as a percentage. Measure it per release once production defects have had time to surface - typically 30 to 90 days after shipping.
What is a good pass rate?
There is no universal number - it depends on where you are in the cycle. Early test runs at 70-80% are normal; an exit-gate run should typically clear 95% with zero open critical defects. The trend matters more than the snapshot: a pass rate that climbs run over run is health, a flat one is churn.
Which size unit should I use for defect density?
The one your team already tracks. KLOC (thousand lines of code) is the classic for codebases, function points for formal estimation shops, and user stories or requirements for agile teams. The unit matters less than consistency - density is only meaningful when compared across releases measured the same way.
Tired of collecting these numbers by hand?
Every input this calculator asks for - executions, pass/fail counts, defect links - is something BesTest records automatically while your team tests inside Jira. Reports and dashboard gadgets turn them into live charts your stakeholders can check without asking you.
Free for teams up to 10 users. All features included.
More free tools
UAT Test Plan Generator
Answer a form, get a complete UAT test plan: scope, entry and exit criteria, schedule, roles, scenarios, defect process, risks, and sign-off. Export to Word, Markdown, or PDF.
UAT Sign-off Sheet Generator
Generate a formal UAT sign-off document: results summary, acceptance criteria, defect dispositions, decision, and stakeholder signature blocks. Print it or export Word/Markdown.
Requirements Traceability Matrix Generator
Paste your requirements and test cases, click to map coverage, and get a color-coded traceability matrix with gap detection. Export CSV or Markdown.
Test Case Template Generator
Write structured test cases with numbered steps and expected results, then export them as Jira-importable CSV, Word, Markdown, or a printable run sheet.
Pairwise Test Case Generator
Enter your parameters and values, get the minimal set of test combinations that covers every value pair. Hundreds of combinations become a dozen tests.
Boundary Value Analysis Calculator
Enter a field's valid range and precision, get its equivalence partitions plus 2-point or 3-point boundary values with expected results.