# Run your first test

Once Playwright code has been generated, run the test against your target site.

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 progress while the test is queued, set up, executed, and finalized.

## 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 runner is usually enough for a public or staging site. If your application is private, behind a VPN, or only reachable from your team's network, review [Runners](/runners.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.                                 |
| Setting up | The runner is preparing dependencies and browser tools.      |
| Running    | Playwright is executing the test.                            |
| Finalizing | TestVibe is collecting result data and artifacts.            |
| Passed     | The test completed successfully.                             |
| Failed     | The test found a problem or could not complete successfully. |
| Cancelled  | The run was stopped before completion.                       |

If the status looks stuck, see [Workflow still running or stuck](/troubleshooting/workflow-running-or-stuck.md) and [Troubleshoot runners](/runners/troubleshooting-runners.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: 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/quickstart/run-first-test.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.