Read Pass/Fail Status
TestVibe shows status at two levels:
- the run status, which describes the whole run
- the test row status, which describes an individual scenario or test
Start with the run status, then drill into Tests tab to understand which rows created that outcome.
Result states
| State | Meaning |
|---|---|
| Passed | The run or test completed successfully. |
| Failed | At least one test failed, or the run could not complete successfully. |
| Cancelled | The run was stopped before it finished. |
| Skipped | A test did not complete. It may not have started, or it may have been cancelled after starting. Check the run-level context; it is not a pass. |
| Queued or in progress | The run is still active and the final result is not ready yet. |
| Unavailable | TestVibe does not have enough result data to show the row or artifact yet. |
Where counts appear
You can find result counts in several places:
| Location | What to use it for |
|---|---|
| Run list | Quickly compare recent runs and find failed or cancelled runs. |
| Run summary | Confirm counts, duration, and environment; expand Metrics for more statistics. |
| Tests tab | Inspect each scenario row and open details. |
| Metrics | Explore the statistics available for this run. |
When a run fails before any test executes
If a run fails before the cloud test session produced any per-scenario results (for example, setup or dependency installation failed), TestVibe still shows an honest terminal state — the recorded failure reason when one was captured, plus Re-run and Ask Assistant actions — instead of leaving the run detail looking blank or stuck.
Mixed outcomes
A run can fail even when most tests pass. Treat a failed run as a signal that at least one selected test or setup step needs attention.
Examples:
| Pattern | What it usually means |
|---|---|
| One failed row | Start with that test's details and evidence. |
| Several failures in one group | Check the shared feature flow or data for that group. |
| Many tests fail at the same step | Check login, environment state, or common prerequisites. |
| Only one browser or configuration fails | Review viewport, browser behavior, or configuration-specific setup. |
For failure triage, continue to Inspect failed steps.