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.
Glossary: testing terms, defined by implementation
Every term below is defined the way MC Testing actually implements it — with the formula, the threshold or the safety rule from the platform's own code, not a generic dictionary meaning. If a report from this platform uses one of these words, this is precisely what it means.
Coverage
How much of what was planned was actually executed — always reported separately from the pass rate, so a high score on thin evidence cannot hide.
Flaky Test
A test whose result flips between pass and fail across runs without the product changing — measured from result history, never guessed, and never silently deleted.
Waiver
A recorded, owner-owned decision to accept a known risk — visible in every report, time-boxed by a review date, and never a way to make a critical blocker disappear.
Leak Scan
A safe, read-only sweep that checks whether sensitive files — .env, .git, backups, data exports — are publicly reachable on a product's web surface.
Tap Target
The clickable size of an interactive element on a phone. MC Testing flags anything under 40×40 CSS pixels on a 390px mobile viewport.
Provisioning (Test-Account Self-Provisioning)
How MC Testing gets its own TEST-QA account: it signs itself up where signup allows, and stops for owner credentials — via a secret store only — where verification blocks it.
How MC Testing implements “Provisioning (Test-Account Self-Provisioning)”
Why definitions matter here
A readiness report is only as trustworthy as the meanings behind its words. When MC Testing says a product is “not ready”, that is a gate outcome — an open critical finding, a confirmed exposure, a failing P0 case — not a mood. When it says coverage is 40%, that is a counted ratio of executed to planned cases, shown separately from the pass rate so thin evidence cannot hide behind green ticks. Pinning these definitions publicly, next to the profiles and packs that produce the evidence, is part of how the platform stays honest: anyone can check a report against the rules that produced it.