Choose Browser, Viewport, and Configuration
Run configurations control how Playwright opens your application. They define settings such as browser, viewport, screenshots, video, traces, reporters, and other execution options.
For Playwright, choose a configured device profile or an advanced configuration. Assistant runs instead offer built-in Desktop, Tablet, and Mobile profiles.
What a run configuration controls
Most teams use configurations to answer questions like:
| Question | Example |
|---|---|
| Which browser should run? | Chromium, Firefox, WebKit, or a named project. |
| What screen size should be used? | Desktop, tablet, mobile, or a custom viewport. |
| What evidence should be saved? | Screenshots, videos, traces, console logs, and network records. |
| How should tests report results? | HTML, JSON, JUnit, blob, or console output. |
New projects include desktop, tablet, and mobile configurations with screenshots, video, and traces enabled. Existing projects can have different settings. See supplied browser profiles for the current template.
Choose a configuration for a run
- Open Runs.
- Select New run.
- Choose the tests you want to execute.
- Under Environment, pick a configured environment (or a Custom URL).
- Under Device profiles, choose the profiles to run. Expand Advanced configurations for the full Playwright configuration list.
- Optionally expand Run options to control concurrency and retries.
- Start the run.
Every configuration you select is attached to that run. When you re-run the same test later, confirm the configuration still matches the environment and browser coverage you want.
Run options: how many scenarios run at once
The composer's Run options concurrency control decides how many scenarios TestVibe runs concurrently against the target site for that one run:
| Option | Behavior |
|---|---|
| Auto | Uses the project's default concurrency (Settings → Playwright). |
| Sequential | Runs one scenario at a time, useful when the target can't handle parallel traffic or you're debugging shared state. |
| Custom | Sets an explicit concurrency cap for this run only, without changing the project default. |
Leaving concurrency untouched sends no override, so the project's configured default concurrency applies exactly as it would without picking anything.
Browser and viewport strategy
Use a small set of clear configurations instead of many overlapping options.
| Configuration type | Use it for |
|---|---|
| Desktop default | Fast daily validation in the team's primary browser size. |
| Responsive | Mobile or tablet layouts where navigation and layout behavior changes. |
| Cross-browser | Compatibility checks across browser engines. |
| Debug | More evidence, lower parallelism, or settings that make failures easier to inspect. |
| Release | Broader coverage before a release or deployment. |
Manage configurations
Open Settings → Playwright to review the existing configuration cards. Open a card's editor to change its file. This screen does not add configuration files; to create another one, follow Add a custom Playwright configuration.
Generation config chooses the configuration used when generating and verifying a test. Runs default config(s) chooses the configurations initially selected in a new run; you can change that selection in the run composer.
The project-wide controls are:
- Expect timeout (ms) under Assertion timeout: how long an assertion waits for the expected state. The default is 30,000 ms; the supported range is 1,000–120,000 ms.
- Test timeout (seconds): the maximum duration of one scenario. The default is 300 seconds; the supported range is 15–600 seconds.
- Concurrent scenarios: limits scenarios running at once against the site. Leave it empty to use runner defaults, or enter 1–64. A run's Run options can override this value for that run.
Choose Save to keep project-wide changes. Review timeouts before raising them: a longer timeout can help a slow but valid flow, but it also takes longer to report a stuck test.
For runner selection, see Runners.