> 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.md).

# Run Tests

Use this section when you are ready to execute generated tests against your application.

TestVibe runs tests in isolated cloud test sessions. The session prepares the environment, Playwright opens your target site, and TestVibe streams status and evidence back into the app.

![The Runs view](/files/gpRetP1tfA6eNA4Jfsu6)

## Common Tasks

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Run one test</strong></td><td>Start with a single scenario when you want fast feedback.</td><td><a href="/pages/bmM92gylZYZkQfqgSjZ4">/pages/bmM92gylZYZkQfqgSjZ4</a></td></tr><tr><td><strong>Run a group</strong></td><td>Execute related tests for a feature area or user journey.</td><td><a href="/pages/Vez001ipTEOEDpGSORKD">/pages/Vez001ipTEOEDpGSORKD</a></td></tr><tr><td><strong>Run the full suite</strong></td><td>Run every selected test in the project.</td><td><a href="/pages/ebtVfid5NIZyIuilJikD">/pages/ebtVfid5NIZyIuilJikD</a></td></tr><tr><td><strong>Understand status</strong></td><td>Follow queued, setting up, running, finalizing, passed, failed, and cancelled states.</td><td><a href="/pages/TQG3WvAwg1TYlzxEpYom">/pages/TQG3WvAwg1TYlzxEpYom</a></td></tr></tbody></table>

## Before You Run

Check these items first:

| Check                | Why it matters                                                                                                               |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Target site URL      | The runner must be able to open the app you are testing.                                                                     |
| Generated test code  | Playwright code needs to exist before TestVibe can execute it.                                                               |
| Browser and viewport | These settings control how Playwright opens the page.                                                                        |
| Reachability         | The cloud session must be able to reach the site — private apps need a [tunnel device](/account-settings/tunnel-devices.md). |
| Secrets              | Login credentials or API keys must be configured when the test needs them.                                                   |

To run journeys under load instead of once, see [Load Testing](/load-testing.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.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.