Reporting & Quality
Quality Gates
Quality gates are automated pass/fail checkpoints — pass rate, coverage, and defect thresholds — attached to a milestone, so "is this release ready?" has a real, current answer instead of a checklist someone eyeballs before shipping.
Product news and testing tips.
Why it matters
A build that's ‘probably fine’ still ships
Without a hard threshold, a risky release slips through because no single person wants to be the one who blocks it.
Manual sign-off doesn't scale
Someone eyeballing a test report before every release works for a while — then a release ships on a Friday and nobody checked.
One threshold isn't one severity
A single “pass rate must be 95%” rule can't tell a cosmetic label bug from a payment outage.
How it works
Configure thresholds on a milestone, mark each as blocking, warning, or informational, and Qualflare evaluates them continuously against the milestone's linked launches — visible on its Health tab.
Release Readiness — quality gates
| Gate | Threshold | Current | Severity | Status |
|---|---|---|---|---|
| Pass rate | ≥ 95% | 97.2% | Blocking | |
| Critical defects | = 0 | 1 open | Blocking | |
| Coverage | ≥ 80% | 76% | Warning | |
| Defect resolution | ≥ 90% | 94% | Warning |
What you get
Configurable thresholds
Set thresholds on pass rate, coverage, critical defects, high defects, and defect resolution rate — pick what "ready" means for each release.
Blocking, warning, or informational
Mark each gate as blocking (stops the release), warning (flags it), or informational (just visible) — not every check needs to be a hard stop.
Attached to milestones
Gates evaluate against a milestone's linked launches, so “Release Readiness” or “Sprint Completion” has a real, current answer instead of a stale checklist.
One weighted progress score
Coverage, pass rate, and defects roll up into a single overall progress score, so a milestone’s health is one number, not five separate charts.
Example: a Release Readiness gate set
A typical "Release Readiness" gate set combines a hard blocker with a couple of softer warnings:
| Gate | Threshold | Severity |
|---|---|---|
| Pass rate | ≥ 95% | Blocking |
| Critical defects | = 0 | Blocking |
| Coverage | ≥ 80% | Warning |
| Defect resolution | ≥ 90% | Warning |
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
- Milestones & Release Health
- Quality gates in CI/CD
- AI quality gates: governing an automated decision
- How to add a quality gate to your CI pipeline
- Glossary: quality gate
Frequently asked questions
What is a quality gate?
A quality gate is an automated pass/fail checkpoint that blocks (or flags) a release based on configurable thresholds — pass rate, test coverage, and open defect counts by severity — rather than relying on someone manually reviewing a report before every ship.
How is a milestone's overall progress calculated?
Overall Progress = (Coverage Score × 0.3) + (Pass Rate Score × 0.4) + (Defect Score × 0.3). The Defect Score weights open defects by severity — Critical counts 4×, High 3×, Medium 2×, Low 1× — so a handful of critical bugs drags the score down far more than the same count of low-severity ones.
What happens when a blocking gate fails?
A failing blocking gate marks the milestone as not release-ready — it's a visible signal in the milestone's Health tab, meant to stop a release conversation before it starts rather than silently gate a deploy pipeline. Warning gates flag the issue without blocking; informational gates are visible-only.
Can I have different gates for different milestones?
Yes. Typical setups use a lighter gate set for sprint completion (e.g. pass rate only) and a stricter set for release readiness (pass rate, zero critical defects, and a coverage floor) — configure whatever combination fits each milestone.
Do quality gates work in CI/CD?
Quality gates live on the milestone's Health tab in Qualflare; to enforce a gate directly inside a CI pipeline (failing the build itself), pair it with a pass-rate or flaky-count check in your pipeline config — see the CI quality gates setup guide for copy-paste examples.