Run One Test

The same single-test run from a terminal: list the generated suite, dispatch one feature to a cloud sandbox with --wait, and get every test with its timing back before the command exits.

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, cloud test session, 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 cloud test session should open.
Run configuration	The browser, viewport, and Playwright settings for the run.
Site access	The cloud test session must be able to reach the site; use a tunnel device for private apps.
Secrets	Any credentials or API keys the test needs, stored in Settings > Variables & Secrets.

Start from Features

1. Open Features.
2. Select the test you want to run.
3. Choose the run action for that test.
4. Confirm the Environment.
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 run is created.

A generated feature's header also shows its own run pill (passed, failed, or running). Selecting it does not open the whole run — it jumps straight to that feature's own Runs tab and expands that feature's part of the run.

Start from Runs

You can also start from the Runs view — this composer is the same one every "Run" action opens:

1. Open Runs.
2. Select New Run.
3. In the test list, check only the test you want to execute.
4. Under Environment, pick a configured environment (or a Custom URL).
5. Select one or more Run Configurations.
6. Optionally set Execution — Auto (recommended), Sequential — one at a time, or Custom — to control how many scenarios run at once. For a single test this rarely matters; it becomes more useful when you widen the selection later.
7. 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 cloud test session has produced an execution plan.

Every run gets its own deep link, so the browser's address bar (and any link you copy from the Share menu) reopens that exact run — useful for pointing a teammate straight at a result instead of describing how to find it.

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 or selected configuration is ready.

From the command line

The same run can be dispatched from a terminal or a CI job, with no browsers or Playwright installed locally — the tests still execute in a cloud sandbox:

testvibe run "Sign in" --wait

--wait blocks until the run finishes, prints each test with its timing, and exits non-zero if any of them failed, so it can gate a CI step directly. Without --wait the command dispatches the run and returns immediately.

Setting up the CLI and its API key is covered in CLI & API keys.

For status details, see Understand live run status. For result evidence, see Review Results.