> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/run-tests/understand-live-run-status.md).

# Understand Live Run Status

TestVibe shows live run status while the cloud test session is prepared, Playwright executes the selected tests, and the session uploads evidence.

Use the live status to understand whether the run is waiting, setting up, actively testing, finalizing artifacts, or finished.

## Run states

| State         | What it means                                                                                                                                                                                                                                                               |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Queued        | TestVibe has accepted the run, but a cloud test session has not started executing it yet.                                                                                                                                                                                   |
| Setting up    | The cloud test session is preparing the environment, installing dependencies, or accepting the run configuration.                                                                                                                                                           |
| Running tests | Playwright is executing the selected tests against the target site. How many scenarios run at once is controlled by the run's **Execution** setting — **Auto** (the project default), **Sequential** (one at a time), or a **Custom** cap, chosen when the run was started. |
| Finalizing    | The session is collecting results, screenshots, videos, traces, logs, and summary files.                                                                                                                                                                                    |
| Passed        | All executed tests completed successfully.                                                                                                                                                                                                                                  |
| Failed        | One or more tests failed, or the run could not complete successfully.                                                                                                                                                                                                       |
| Cancelled     | The run was stopped before completion.                                                                                                                                                                                                                                      |

## Per-test rows

At the start of a run, TestVibe may only show the selected feature files or test scope. Detailed executable rows appear after the cloud test session creates the execution plan.

If the run composer had more than one **Run Configuration** selected, each test runs once per configuration — the row count reflects tests × configurations, not just the test count.

During execution, rows update as Playwright reports status. After the run finishes, open failed rows to inspect evidence such as screenshots, videos, traces, console output, and network details.

## Why statuses can update at different times

TestVibe receives information from run lifecycle events and from cloud test session status updates. These signals usually arrive close together, but they can land a few moments apart.

For example, the session may report that testing is complete while TestVibe is still processing final result files. Give finalizing runs a short moment to settle before deciding the result is missing.

## What to do when a run looks stuck

| Where it is stuck | What to check                                                                            |
| ----------------- | ---------------------------------------------------------------------------------------- |
| Queued            | Session capacity and plan limits; queued runs usually start within moments.              |
| Setting up        | Dependency installation, project secrets, package lock issues, and configuration errors. |
| Running tests     | Target site availability, login state, test data, and long-running UI steps.             |
| Finalizing        | Artifact upload and trace/video size.                                                    |

If a run is clearly no longer useful, see [Cancel or re-run tests](/run-tests/cancel-or-rerun-tests.md). For execution environment issues, see [Troubleshoot runners](/runners/troubleshooting-runners.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/run-tests/understand-live-run-status.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.