Skip to main content

Run

Help URL: /reference/forms/run

Purpose​

Select one or more generated tests and run them against your site in an isolated cloud test session.

Quick Start​

  1. Confirm Site URL (defaults to the project's site URL).
  2. (Optional) Pick Browser and Viewport.
  3. Select tests in the Tests picker.
  4. Click Start to dispatch the run.

How Runs Work​

When you start a run, TestVibe materializes your project's tests into a bundle and dispatches it to an isolated cloud test session. The session runs Playwright against your Site URL; per-scenario and per-step status, then screenshots, videos, traces, and console/network evidence, stream back into the Runs view live. There is no CI pipeline to host and no runner to configure.

Selecting Tests​

  • All tests: by default, the form can pre-select all leaf tests.
  • Group selection: a group can be preselected (for example from elsewhere in the app).
  • Direct selection: selecting a single test runs only that test.
  • The form also supports "best-effort" selection by a selector string (used by the Assistant tool integrations).

Configuration, Browser, and Viewport​

TestVibe supports Playwright configurations stored with the project in TestVibe's cloud:

  • Use Select config to open PlaywrightTestConfiguration.
  • The Browser and Viewport fields on this form are treated as "simple overrides":
    • They are persisted back into the selected Playwright config (best-effort) so future runs can reuse them.
    • The run is driven by the project's Playwright configuration; these fields update that config rather than being sent as separate inputs.

If you need deeper config options (headers, proxy, tracing, reporters, web server), use PlaywrightAdvancedOptions.

Device Profiles (Viewport Presets)​

When prefilled (for example by the Assistant), device profiles map to viewports:

  • mobile-portrait -> 390x844
  • mobile-landscape -> 844x390
  • tablet -> 820x1180
  • desktop-1080p -> 1920x1080

Troubleshooting​

  • "Select at least one test": choose one or more tests in the picker before clicking Start.
  • Live status not updating: give a finalizing run a moment to settle, then refresh the Runs view; see Understand live run status.
  • Wrong site under test: update Site URL and restart the run.

Notes​

  • TestVibe shows a short guided tour for this form once per browser (cookie testvibe.tour.run).