Skip to main content

Understand Live Run Status

A run's overall status describes the whole job. Each row in Tests describes one scenario at one device profile or configuration.

Follow a group run from queued through preparing, running, and collecting evidence, see how an Assistant scenario reports its activity, watch a loading message and a refresh error resolve with Retry, filter the rows to find a scenario, and read the completed states, including a Flaky test that passed on a retry.

While a run is active​

  • Queued means the job has been accepted and is waiting to start.
  • Preparing or setup progress means the execution environment is starting.
  • Running means tests are executing. Some scenarios may still be Pending while others are Running, Passed, Failed, or Skipped.
  • Finalizing activity means results and captured evidence are being collected.

Assistant scenarios show the latest reported activity and elapsed time in their details. The elapsed clock alone is not proof of new progress; read the activity and step results. Playwright concurrency comes from Run options or the project default; Assistant scenarios run sequentially.

Loading results is separate from execution​

A Loading results… message means TestVibe is fetching the result data. It does not mean there were zero tests or that the run failed. If fetching fails, Retry reloads the results without starting another run. During a refresh, already loaded rows remain visible; a refresh error says when you are seeing the last results.

Use search, the status filter, and the page controls to find a test. Result rows can arrive after the run summary. Open details remain tied to the same scenario as its live result updates.

Completed states​

Passed means the executed checks passed. Failed can mean a test failed or setup prevented execution. Cancelled means the run was stopped. A Skipped scenario did not complete. It may not have started, or it may have been cancelled after starting. Read the run-level context if no useful scenario error was captured.

A run can fail while most tests pass, or fail before any scenario executes. Do not count pending or skipped rows as passes. Flaky marks a test that failed and then passed on a retry.

If progress stops, check Run still running or stuck. If the run has finished, continue to Read pass/fail status.