Run Your First Test
Pick one generated test out of a group, start a run against the live site, watch it move through queued and running, and land on an all-green summary with its duration and credit cost.
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
- Select the generated test.
- Choose the action to run the selected test.
- Confirm the site URL.
- Keep the default browser, viewport, and configuration unless you need something specific.
- Start the run.
- 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 before running a larger suite.
After the quickstart, learn more in Choose browser, viewport, and configuration.
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.
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.