Test Management
Milestones & Release Health
A milestone tracks testing progress toward a specific target — a release, a sprint, a compliance sweep. Launches, defects, and runs group under it, and its Health tab answers "are we ready" with real data, not a status meeting.
Product news and testing tips.
Why it matters
Release readiness is a guess
Someone asks “are we ready to ship v2.8” and the honest answer is “let me check five different tabs first.”
No shared reference point
Testing for a release happens across a dozen launches, and nobody's tracking whether it's actually converging.
Health lives in a spreadsheet
The real status of “is this release healthy” lives in someone's head, or a doc that's already out of date by the next standup.
How it works
Create a milestone for a release or sprint, then link test plans and launches to it as testing happens. The Overview tab tracks pass rate, defect count, and coverage over time; the Health tab breaks status down suite by suite.
Qualflare| Name | Branch | Environment | Date | Status |
|---|---|---|---|---|
#1201Login with SSO provider | main | Staging | Mar 28, 12:00 PM | 92% |
#1200Bulk data import validation | main | Staging | Mar 28, 12:00 PM | 58% |
#1199Dashboard chart rendering | fix/sso-redirect | QA | Mar 28, 12:00 PM | 93% |
#1198API rate limiting under load | fix/sso-redirect | Staging | Mar 27, 12:00 PM | 93% |
#1197File upload with virus scan | release/2.8 | QA | Mar 27, 12:00 PM | 52% |
#1196Report PDF generation | release/2.8 | Staging | Mar 27, 12:00 PM | 87% |
#1195Database migration rollback | main | Staging | Mar 26, 12:00 PM | 88% |
#1194User profile serialization | main | QA | Mar 26, 12:00 PM | 74% |
#1193Stripe webhook retry logic | main | Staging | Mar 25, 12:00 PM | 47% |
#1192WebSocket reconnection flow | main | Staging | Mar 25, 12:00 PM | 89% |
What you get
One goal marker, one place
Group everything testing a release or sprint — launches, defects, runs — under a single milestone.
A Health tab, not a spreadsheet
Suite-by-suite run status computed from real, current data — not something a person has to maintain.
A weighted progress score
Coverage, pass rate, and defects roll up into one Overall Progress number, so health is a figure you can track over time, not five separate charts.
Quality gates attached
Configure blocking, warning, and informational thresholds directly on the milestone — see Quality Gates.
Quality gates on a milestone
A milestone can carry its own quality gates — configurable thresholds on pass rate, coverage, and defect counts, each marked as blocking, warning, or informational. A "Release Readiness" milestone might hard-block on zero critical defects while a "Sprint Completion" milestone only warns on the same condition — see the full mechanics on the Quality Gates page.
Ready to see it on your own test results?
Start free with Qualflare — connect your pipeline, upload a run, and see this in minutes.
Get Started FreeRelated features
Frequently asked questions
What is a milestone?
A milestone is a goal marker that tracks testing progress toward a specific target, such as a release or sprint completion. It represents a significant testing checkpoint — tracking readiness to ship, identifying blockers, and showing how quality trends over time.
What's the difference between a milestone and a test plan?
Test plans schedule and coordinate test execution — which cases run, when, and how. Milestones track progress toward a goal, like a release. A single milestone can span multiple test plans (a smoke plan running daily, a full regression plan running weekly, both feeding into the same release milestone).
How is milestone health calculated?
Overall Progress = (Coverage Score × 0.3) + (Pass Rate Score × 0.4) + (Defect Score × 0.3), where the Defect Score weights open defects by severity. See Quality Gates for the full breakdown.
What tabs does a milestone have?
Overview (progress and status breakdown), Health (per-suite run status), Launches (every test launch linked to this milestone), and Comments (team discussion).