How Pulse turns test runs into release confidence
Pass rate is not confidence. Pulse blends per-area execution snapshots with live Blueprint coverage, surfaces Likelihood × Impact risk, and keeps KPIs, heatmap, and trends on one lens.
Nimra Naseem
Senior QA Engineer
Executives ask a simple question before ship: how confident are we? Engineering answers with dashboards of pass rates. Those numbers feel precise and often mislead.
Pass rate collapses many stories into one: a flaky area and a rock-solid area can look identical if both “mostly pass.”
Two sources, one dashboard
Pulse is a continuous health dashboard for your product, scored per Blueprint area. It blends two sources that update on different cadences:
| Source | What it measures | When it updates |
|---|---|---|
| Execution | How linked tests actually ran in orchestrations | When a run finishes and Pulse stores a snapshot |
| Coverage | Spec↔area and spec↔test link health from your Blueprint | Live when you change links — no new run required |
The dashboard opens after at least one finished orchestration produces an execution snapshot. Coverage then layers into the KPI strip and trends; the area heatmap colours from execution health so the map stays tied to what actually ran.
The lens keeps every panel honest
The lens is the saved view of the dashboard. It chooses:
- Which health signals feed the blend (test execution, spec–area, spec–test)
- Environment, range (7d / 30d / 90d / custom), and tags
- Which runs on the timeline you are comparing
KPI strip, heatmap, and trend chart stay aligned to that lens — so you are never comparing apples to oranges across panels.
States you can defend in a go/no-go
Each area lands in Healthy, Warning, Critical, Unknown, or Ignored (archived areas stay out of the overall score). Colour is never the only cue: labels and icons keep the board usable under pressure.
Execution snapshots also carry a Likelihood × Impact risk read (1–25) for the highest-area-risk KPI — useful when pass rate looks fine but one critical subtree is concentrating danger.
Trends that answer “what is dragging us?”
Break the trend chart down by:
- Overall project health
- Orchestration (which workflow is hurting the score)
- Area (where risk concentrates)
- By health score when coverage signals are in the lens — including days with no execution snapshot
Drill a heatmap tile and the trend re-scopes to that subtree. Clear the selection to return to project-wide view.
Wiring Pulse into the release ritual
- Before code freeze: close Gaps on high-criticality Blueprint nodes.
- During the release candidate: watch orchestration’s live area heatmap.
- At go/no-go: open Pulse with a lens that matches the release environment and tags — not only the CI badge.
- After ship: keep the snapshot history so the next cycle has a baseline.
What changes culturally
Teams stop arguing about “enough tests” in the abstract. They argue about which areas need coverage or healthier runs before the next train. That is a healthier conversation — and it scales with AI-authored change.
Pulse does not replace judgment. It gives judgment a shared, evidence-backed language.
Keep reading
More from the blog.
Why a green pipeline is not a release gate
A passing CI run tells you the checks you already had passed. It does not tell you whether the areas that just changed were ever tested. Here is how to make the pipeline a real gate.
Hamza Abdullah
CEO
Your product needs a coverage map, not another pass-rate chart
Blueprints turn modules, journeys, and services into a living area map — with criticality, specs, tests, gaps, and impact links that Pulse and orchestration can actually use.
Lyba Fatima
Senior QA Analyst
Self-healing is not enough — you still need a coverage map
Healing locators cuts maintenance. It does not tell you which critical journeys are untested when AI ships ten PRs before lunch.
Taimour Shoaib
QA Engineer