> 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/quickstart/run-first-test.md).

# Run Your First Test

Once Playwright code has been generated, run the test against your target site. Each run executes in an isolated cloud test session — there is nothing to install or host.

For the quickstart, run one test first. A single-test run is easier to understand and faster to troubleshoot than a full suite.

## Steps

1. Select the generated test.
2. Choose the action to run the selected test.
3. Confirm the site URL.
4. Keep the default browser, viewport, and configuration unless you need something specific.
5. Start the run.
6. Watch the live status until the run finishes.

If the run starts successfully, TestVibe will show live per-scenario and per-step status while the test is queued, prepared, and executed.

## Browser, Viewport, And Configuration

For your first run, defaults are usually enough.

You can adjust:

* browser
* viewport or device size
* Playwright configuration
* selected tests

The default cloud test session is enough for a public or staging site. If your application is private, behind a VPN, or only reachable from your team's network, set up a [tunnel device](/account-settings/tunnel-devices.md) before running a larger suite.

After the quickstart, learn more in [Choose browser, viewport, and configuration](/run-tests/browser-viewport-configuration.md).

## What Status Means

| Status    | Meaning                                                                               |
| --------- | ------------------------------------------------------------------------------------- |
| Queued    | The run is waiting to start.                                                          |
| Preparing | A cloud test session is being allocated for the run.                                  |
| Running   | Playwright is executing the test, with live per-scenario and per-step status.         |
| Passed    | The test completed successfully.                                                      |
| Failed    | The test found a problem or could not complete successfully.                          |
| Cancelled | The run was stopped before completion.                                                |
| Error     | The run could not complete because something went wrong outside the tests themselves. |

If the status looks stuck, see [Run still running or stuck](/troubleshooting/workflow-running-or-stuck.md).

## If The Run Fails

Do not assume the generated test is wrong immediately. First, review the evidence.

A run can fail because:

* the application has a real issue
* the test data is missing or different than expected
* the site URL is wrong
* the generated selector or assertion needs refinement
* the test instructions were too vague

The next page explains how to inspect the result.

## Next

Continue to [Review your first result](/quickstart/review-first-result.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/quickstart/run-first-test.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.