Skip to main content

​
Overview

A manual run lets you execute a test on demand. When you click Run on a test, you walk through a series of selections to define exactly how that run should behave: which environments to target, which browsers to use, which viewports to test against, and which scenarios to include. Each selection multiplies the number of runs. Selecting two environments and two browsers, for example, produces four parallel runs for that test.

​
What You Can Select

Environments

Select one or more environments to run your test against. Tests run in parallel across all selected environments. At least one environment is required to start a run.

Browsers

Choose which browsers to run your test in: Chrome, Firefox, Safari, or Edge. Selecting multiple browsers runs your test in each one in parallel.

Viewports

Choose desktop, mobile, or both. Viewport selection only affects tests configured to support multiple viewports.

Scenarios

For tests with scenario tables, choose which rows to include. Scenarios can be made environment-specific so different environments run different data sets.

​
How to Run a Test

1

Select a test to run

Navigate to your test suite and click Run on the test you want to execute. This opens a step-by-step flow where you make your selections before starting the run.
Starting a manual run
2

Choose Environments

Select one or more environments to run your test in. Each selected environment will receive its own parallel run. You can only select environments that the suite is configured for. To learn more about how environments work, see Environments. Click Next when ready.
At least one environment must be selected to proceed. If no environments appear, check that your test suite has active environments configured.
Tests can only run in environments the suite is configured for. If you need to add an environment, update the suite settings first.
Choose Environments
3

Choose Scenarios

If your test has a scenario table, you’ll see all available scenarios for each selected environment. Select the rows you want to include. Each environment only shows the scenarios enabled for it, so different environments can run different data sets. Click Next when ready.
Each selected environment must have at least one scenario assigned. A run cannot start if any environment has no scenarios selected.
Scenarios can be made environment-specific directly in the scenario table. See Scenarios for how to set this up.
Choose Scenarios
4

Choose Viewports

If your suite contains tests configured for multiple viewports, you’ll see viewport selection here. Choose desktop, mobile, or both. Click Next when ready.Your viewport selection only applies to tests that support multiple viewports. Tests locked to a single viewport always run on that viewport regardless of what you select here. For example, if your suite contains:
  • Test A — Desktop only
  • Test B — Mobile only
  • Test C — Desktop and Mobile
Selecting Mobile produces: Test A on Desktop, Test B on Mobile, Test C on Mobile. Selecting Desktop and Mobile produces: Test A on Desktop, Test B on Mobile, Test C on Desktop, Test C on Mobile — four runs total. This behaviour also applies to dependencies.
This step only appears when at least one test in your suite supports multiple viewports. To enable this on a test, see Viewports.
Choose Viewports
5

Choose Browser

Select which browsers to run the test in. You can pick one or more from Chrome, Safari, Firefox, and Microsoft Edge. Each selected browser adds a parallel run per environment. Click Next when ready.
Choose Browser
6

Review the Run Summary and Start

The Run Summary shows a breakdown of the total runs about to be created, grouped by environment, test name, scenarios, and run count. You can click any previous step to make changes before starting. When you’re ready, click Start Runs.
Every combination of environment, browser, and scenario produces a separate parallel run. For example: 2 environments x 2 browsers x 3 scenarios = 12 runs.
If a test has dependencies, the Run Summary will automatically include the parent tests that need to run first. For example, if Test C depends on Test B which depends on Test A, running Test C will show Test A, Test B, and Test C in the summary.
Run Summary