# Run one test

Run one test when you want to verify a new scenario, check a recent change, or investigate one failing case without waiting for a larger suite.

Single-test runs are the safest first step after generating Playwright code. They confirm that the target site, runner, configuration, and test steps all work together.

## Before you start

Make sure the test has generated Playwright code. A Gherkin feature alone is not enough to execute in Playwright.

You also need:

| Item              | What to check                                                           |
| ----------------- | ----------------------------------------------------------------------- |
| Site URL          | The application URL the runner should open.                             |
| Run configuration | The browser, viewport, and Playwright settings for the run.             |
| Runner            | A GitHub-hosted or self-hosted runner that can reach the site.          |
| Secrets           | Any credentials or API keys the test needs to sign in or call services. |

## Start from the Test Suite

1. Open **Test Suite**.
2. Select the test you want to run.
3. Choose the run action for that test.
4. Confirm the **Site URL**.
5. Select one or more **Run Configurations**.
6. Start the run.

TestVibe opens the run details so you can follow progress as soon as the workflow is created.

## Start from Runs

You can also start from the Runs workspace:

1. Open **Runs**.
2. Select **New Run**.
3. In the test list, check only the test you want to execute.
4. Enter the **Site URL**.
5. Choose the run configuration.
6. Start the run.

Use this path when you want to choose the test and configuration in one place.

## Watch the result

While the run is active, TestVibe shows the run moving through live states such as queued, setting up, running, and finalizing. Individual test rows appear once the runner has produced an execution plan.

After the run finishes:

| Result    | Next step                                                                                      |
| --------- | ---------------------------------------------------------------------------------------------- |
| Passed    | Run the related group or add the test to a larger regression run.                              |
| Failed    | Open the failed row and review screenshots, videos, traces, console logs, and network details. |
| Cancelled | Re-run when the site, runner, or selected configuration is ready.                              |

For status details, see [Understand live run status](/run-tests/understand-live-run-status.md). For result evidence, see [Review Results](/results.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/run-one-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.