Run Tests

Run saved Playwright code, or choose an Assistant run to follow Gherkin or Markdown instructions directly against your app.

TestVibe runs tests in isolated cloud test sessions. The session prepares the environment, Playwright opens your target site, and TestVibe streams status and evidence back into the app.

Open Runs, start a New run with Playwright or an Assistant run, choose one test, a group, or the full suite, check the site URL, browser and viewport, reachability, and secrets, then follow the run from queued through running to passed and cancel or re-run it from the result page.

Common Tasks

Run one test

Start with one test feature when you want focused feedback.

Run a group

Execute related tests for a feature area or user journey.

Run the full suite

Run every selected test in the project.

Understand status

Follow queued, setting up, running, finalizing, passed, failed, and cancelled states.

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.
Run method	Playwright needs saved executable code. Assistant runs need saved instructions and use Assistant credits.
Browser and viewport	These settings control how Playwright opens the page.
Reachability	The cloud session must be able to reach the site — private apps need a tunnel device.
Secrets	Login credentials or API keys must be configured when the test needs them.

To run journeys under load instead of once, see Load Testing.