Skip to main content
TestPulse reports the latest result of each test and reduces them to a single execution verdict. Here is exactly how.

​
Outcomes

OutcomeMeaningCounts as
PassedThe test ran and passed.Passed
FailedThe test ran and failed.Not OK
BlockedThe test could not run (a blocker).Not Run
Not ApplicableThe test does not apply to this scope.Not Run
Not ExecutedScheduled but not run yet.Not Run
NoneNo result at all for the point.Not Run

​
The “latest result”

A test point can have a history of results. TestPulse takes the most recent one (by completion date) — that is the outcome and the last run date you see. Change the scope and the latest is recomputed for that plan, in memory, with no new read.

​
From outcomes to a verdict

The execution verdict is a pure reduction with strict precedence:
  1. Any Failed → Not OK
  2. Otherwise any non-passed (Blocked, Not Applicable, Not Executed, None) → Not Run
  3. Only 100% Passed → Passed
  4. No linked test → Not covered
There is no “partial”: one failure is enough to make a story Not OK. The verdict always shows an icon + label, so it reads correctly in light or dark themes and for colour-blind users, and it never recolours the Coverage pill.
None vs Not Executed: None means the point has no result object at all; Not Executed means a result exists but the run hasn’t happened. Both read as Not Run.

The Test coverage tab

Where the verdict appears.

Traceability & hierarchy

The bug behind a failure.