Run, test and exploration statuses

What Queued, Running, Passed, Failed, Canceled and Skipped mean for runs and tests, why a test waits, the statuses of an exploration, of Self-driving’s reviews and investigations, of Inbox items and of findings.

Test statuses

A test is one test case executed once, inside a run.

Status	Meaning
Queued	Waiting for a browser. The card says why (below).
Running	Its browser is open and working through the steps.
Passed	Every step ran and the Expected Outcome holds.
Failed	A step failed, the Expected Outcome didn’t hold, the time ran out, or login failed. The failure reason says which.
Canceled	Its run was canceled. A test that hadn’t started didn’t run and isn’t charged.
Skipped	Its test case was switched off while it waited. It didn’t run and isn’t charged.

Why a test is waiting

Line on the card	Meaning
Waiting for a browser (N ahead)	Other tests are first in line for a browser.
Next in line for a browser	It starts as soon as a browser is free.
Waiting for the login on credential “…”	A test that shares its login is signing in; this one then reuses that login.
Login limit for credential “…” reached	Every browser the credential allows at once is in use.
One test at a time on the Free plan	Another test of the organization is running.
Retrying: Testmode’s AI model is temporarily unavailable	A failure on our side; the test is tried again.
Retrying: Testmode’s browser session failed	The same, for the browser.

Run statuses

A run’s status rolls up from its tests.

Status	Meaning
Queued	No test has started yet.
Running	At least one test is running or waiting, and the run isn’t finished.
Passed	Every test that ran passed.
Failed	At least one test failed.
Canceled	Someone clicked Cancel run. Finished tests keep their results.
Skipped	The run didn’t start: a scheduled run without enough credits, with nothing to run, while the schedule’s previous run was still in progress, while testing was paused, or on the Free plan. Or every test was skipped. The run page says why.

A run started from the app, CI or an agent never ends Skipped for lack of credits: it is refused before it starts instead, with a message saying so.

Exploration statuses

Status	Meaning
Queued	Waiting to start. One exploration runs per project at a time.
Exploring	The agent is visiting pages and trying things on them. The live browser and Pages visited fill in.
Analysing	The crawl is over; the agent compares what it found with your suite.
Ready for review	Suggestions are waiting for you to add or decline.
Finished	The agent found nothing to suggest from the pages it could read.
Applied	Its suggestions have been added to the suite.
Failed	It couldn’t finish, for example because no page could be read. The message says why.
Canceled	Someone clicked Stop.

Reviews and investigations

Self-driving’s reviews and investigations of failed runs show these in Activity:

Status	Meaning
Queued	Waiting to start.
Working	Under way. Stop ends it after its current step.
Done	Finished. A review shows its update; an investigation its verdicts.
Failed	It couldn’t finish. The row says why.
Stopped	Someone stopped it.

Inbox items

Tab	Holds
Needs you	Items waiting for a decision, grouped as Needs you and Ready to review (a fix that already passed, or an exploration’s suggestions).
Done	Items someone confirmed, marked fixed, applied or answered, and flaky failures Self-driving set aside.
Dismissed	Items someone dismissed. A dismissed item stays dismissed when it happens again.

Findings

Status	Meaning
Untriaged	Nobody has said what it is yet.
Bug, Environment	Triaged and still open.
Fixed, verifying	Someone clicked Fixed; the test’s next passing run verifies it.
Verified fixed	The test passed again after the fix.
Closed	An intended change, a test problem, flaky, an environment that recovered, or closed by hand.

Read run resultsThe evidence behind each status.

How credits are countedWhich statuses use credits.

Track what testing foundFindings and their triage.