Project Quality Score Calculator
Compute a composite quality score for a project by combining test pass rate with a penalty for critical defects found. Use this at the end of a testing cycle or release gate to decide whether the build is fit for deployment.
About this calculator
This quality score blends two dimensions of software quality into a single index. The formula is: Quality Score = (passedTests / totalTests × 100) − (criticalDefects × 5). The first term is the percentage of tests that passed, giving a baseline out of 100. The second term applies a 5-point penalty for each critical defect, reflecting the disproportionate risk they carry compared to minor issues. A score of 100 means all tests passed and no critical defects exist — a perfect build. A score below 0 signals a critically unstable release. Teams typically set a minimum acceptable threshold (e.g., 80) as a release gate, blocking deployment if the score falls below it.
How to use
Suppose your test run recorded 90 passed tests out of 100 total (passedTests = 90, totalTests = 100) and uncovered 3 critical defects (criticalDefects = 3). The calculator computes: (90 / 100 × 100) − (3 × 5) = 90 − 15 = 75. Your quality score is 75. If your release gate is 80, this build would be blocked, and the team knows it must resolve at least one critical defect (raising the score by 5) and pass a few more tests to clear the threshold.
Frequently asked questions
Why does the quality score apply a higher penalty for critical defects than for failed tests?
Critical defects represent issues that can cause data loss, security breaches, crashes, or regulatory violations — failures with consequences far more severe than a standard failing test case. The 5-point multiplier encodes that judgment: one critical defect is roughly equivalent in risk to failing 5 ordinary tests. This asymmetric weighting ensures that a build with a high pass rate but several critical defects cannot slip through a release gate unnoticed. Teams can adjust the multiplier to match their own risk tolerance or severity taxonomy.
What is a good quality score threshold to use as a release gate?
A common industry benchmark is 80 or above for production releases, with 90+ reserved for high-compliance domains like healthcare or finance. A score between 60 and 80 typically warrants further testing and targeted defect resolution before release. Scores below 60 generally indicate systemic quality issues requiring a deeper root-cause analysis rather than a quick fix. Your threshold should be calibrated to your users' risk tolerance and your organization's SLA commitments.
How should I interpret a negative quality score from this calculator?
A negative score means the critical defect penalty outweighs the test pass rate entirely, signaling an unstable or potentially dangerous build. For example, 20 critical defects would subtract 100 points from even a perfect 100% pass rate, yielding a score of 0 or below. A negative result is a hard stop — it should trigger an immediate halt to release activities and a focused defect-triage session. In practice, reaching a negative score suggests that the testing process itself may need to be re-examined to catch critical issues earlier in the cycle.