Readiness Score
A 0–100 score computed only from executed tests by a fixed, auditable formula — plus a rule-based label that a high score can never override.
Definition
A readiness score answers one question: how close is this product to being safe to release, based on evidence? In MC Testing the score is a pure function of executed test results — no executed tests, no score. Cases that were planned but not run never inflate it, and the inputs behind every score are stored with the snapshot so any reader can re-derive the number by hand.
Each category (functional correctness, business logic & data integrity, security, integration & reliability, UI/UX & accessibility, performance, deployment & operational readiness) is scored separately: 100 × the priority-weighted share of passed cases among executed cases, minus penalties for open findings (critical −25, major −10, minor −3). Priority weights are P0 = 4, P1 = 3, P2 = 2, P3 = 1. The overall score is the weighted average of the categories that produced evidence; categories with no evidence are listed as evidence gaps instead of being scored zero or guessed.
How MC Testing applies it
The score is paired with a readiness label decided by gates, in strict precedence: any blocker — an open critical finding, a confirmed public data exposure still open, a failing P0 case, or a mandatory category (security, business logic) below the minimum of 50 — means NOT READY. Otherwise, P0/P1 coverage below 50% means INSUFFICIENT EVIDENCE; an open unwaived major finding means CONDITIONALLY READY; otherwise READY FOR RELEASE. A numerical score never overrides these gates.
Profiles can override the default category weights (functional 25, business 20, security 20, integration 10, UI/UX & accessibility 10, performance 10, deployment 5), and the weights actually used are stored in every snapshot. See also Coverage, Waiver and Flaky Test.