Read Pass/Fail Status

Understand run-level and test-level result states, summary counts, and mixed outcomes in TestVibe.

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 the Features tab to understand which rows created that outcome.

TestVibe completed run results

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 was intentionally not executed, often because a condition or dependency prevented it.
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.
Summary tiles	Confirm total tests, pass rate, duration, and run metadata.
Features tab	Inspect each scenario row and open details.
Charts	Spot patterns by group, project, status, or duration.

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 AI 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.