# Run Tests

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

TestVibe runs tests through GitHub Actions. A runner prepares the environment, Playwright opens your target site, and TestVibe streams status and evidence back into the app.

## 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 repository test suite.</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.                      |
| Runner               | The GitHub Actions runner must be online and able to reach the site.       |
| Secrets              | Login credentials or API keys must be configured when the test needs them. |

For runner setup, see [Runners](/runners.md).


---

# Agent Instructions: 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:

```
GET https://docs.testvibe.com/run-tests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.