Configurations represent the environments you test against — combinations of platforms such as browsers, operating systems, or devices. Linking a test run or session to a configuration records which environment was used and makes it easy to compare results across environments. When you need to run the same tests against multiple environments at once, configurations let you create all the runs in a single step rather than building each one separately.
Platforms and platform groups
Configurations are built from platforms — the individual environment components such as Chrome, Windows 10, or iPhone 15. Platforms are organized into platform groups to keep related items together, for example a "Web Browsers" group containing Chrome, Firefox, Safari, and Edge, or an "Operating Systems" group containing Windows and macOS.
A configuration is a named combination of one or more platforms, such as "Chrome, Windows 10" or "Safari, macOS". The configuration's name is derived automatically from the platforms it contains.
Managing platforms and configurations is done from the Configurations page in the Testmo admin area.
Managing platform groups and platforms
The Configurations page is divided into three sections: Platform groups on the left, Platforms on the right, and Configurations below.
Adding a platform group
Click the + Group button to open the Add platform group dialog. Enter a name for the group and click Add platform group to save. The new group appears in the Platform groups table with its platforms listed under the Platforms section when the group is selected.
Adding platforms to an existing group
Select a group from the Platform groups table, then click the + Platforms button to open the Add platforms dialog. Enter the platform names, one per line, and click Add platforms. The new platforms are added to the selected group.
Editing and disabling platforms
Each platform in the Platforms table has controls to rename it, enable or disable it, and delete it.
Disabling a platform automatically disables all configurations that use it. Any runs, sessions, or automation runs that referenced a disabled configuration retain a link to it, but the configuration is no longer available for new test runs or sessions. A disabled configuration can be re-enabled once all of its platforms are active again.
Deleting a platform removes it permanently and cleans up all associated configurations.
Creating configurations
Click the + Configurations button on the Configurations page to open the configuration creation wizard. The wizard has three steps.
Step 1: Select platforms
Choose the platforms to combine. You select platforms from across your platform groups — for example, pick Chrome and Firefox from "Web Browsers" and Windows 10 and macOS from "Operating Systems". The wizard uses these selections to calculate every possible combination in the next step.
Step 2: Select configurations
The wizard lists all possible combinations from your selected platforms. For the browser and OS example above, this would be Chrome + Windows 10, Chrome + macOS, Firefox + Windows 10, and Firefox + macOS. Select the combinations you want to create. Combinations that already exist as configurations are excluded from the list.
Each configuration is automatically named from the platforms it contains, separated by commas: "Chrome, Windows 10".
Step 3: Choose project settings
Decide which projects can use these configurations:
- The configurations apply to all projects — makes the new configurations available to every project, including projects created in the future.
- The configurations apply to the following projects only — limits availability to the specific projects you select.
Project scope can be changed after creation.
Click Add configurations to create all selected combinations at once.
Managing configurations
The Configurations table shows all configurations with their enabled status and the number of projects they are assigned to. You can search the table and filter it by status, platforms, or projects.
Changing project scope
Select the Edit projects option to change whether that configuration applies to all projects or only specific ones. You can also select multiple configurations and use Assign projects to add projects to the selected configurations, or Remove projects to remove them.
Enabling and disabling configurations
Configurations can be enabled and disabled individually or in bulk. A disabled configuration remains visible in historical runs and sessions but is not available when creating new ones. If a configuration's underlying platforms are re-enabled, the configuration can be re-enabled as well.
Deleting configurations
Deleting a configuration removes it permanently. Existing runs, sessions, and automation runs that used it are not deleted — they remain intact but no longer carry a configuration link.
Using configurations in test runs
Single run
When creating a run using the Add Run dialog, the Configuration field lets you select the environment for that run. Selecting a configuration links the run to that environment.
Once a configuration is selected, an Apply to cases link becomes active next to the field. Clicking it filters the case selection to only test cases associated with that configuration. If cases are already selected, the filter intersects with the existing selection; if all cases are included, the selection is replaced with the configuration-filtered set. This is useful when different environments have different applicable test cases.
Multiple runs
When creating runs using the Add Multiple Runs dialog, each run row has a Select Configurations button. Clicking it opens the Select configurations dialog, where you can choose any number of configurations for that run.
A separate run is created for each selected configuration. A single row in the dialog with three configurations selected becomes three runs on save, each linked to one configuration. This is the fastest way to set up parallel test runs across environments — define the run once and let the configurations multiply it.
In the Select configurations dialog, each configuration can have its own case selection: inherit from the run's base selection, include all cases, or use a custom selection per configuration.
The total number of runs across all rows and configurations cannot exceed 250.
Viewing configuration in a run
The run detail page shows the configuration name in the page header, in parentheses next to the run name. The configuration also appears in the run's About panel and can be used to filter runs on the Runs & Results main page.
Using configurations in exploratory sessions
Configurations work the same way in exploratory sessions as in test runs.
When creating a single session using the Add session dialog, the Configuration field links the session to a specific environment.
When creating multiple sessions using the Add multiple sessions dialog, each session row has a Select configurations option. Selecting configurations for a row creates a separate session for each one. This is useful when you want the same exploratory investigation to happen in parallel across different browsers or devices, with results kept separate per environment.
Using configurations in automation runs
Automation runs submitted via the CLI or API can include a configuration identifier. This links the automated test results to a specific environment, making it possible to track pass/fail rates per configuration in the Reporting Center.
For details on submitting automation runs with configuration data, see About Testmo Automation.
Typical use cases
Cross-browser and cross-platform testing — Create a platform group for browsers and another for operating systems. Generate configurations for each combination you support (Chrome on Windows, Chrome on macOS, Firefox on Windows, and so on). When a release is coming up, use the multiple runs dialog to create a full matrix of runs in a single step.
Mobile device testing — Create a platform group for devices (iPhone 15, Samsung Galaxy S24, Pixel 8) and use configurations to track which device each run covers. Compare pass rates across devices directly from the Runs & Results main page.
Single-environment tracking — Even if you only test on one platform, attaching a configuration to your runs makes the environment explicit in the run record. This is useful for auditing and for reporting that needs to show which environment was used.
Configuration-specific case selection — Associate test cases with specific configurations in your repository. When a tester selects a configuration on a run and clicks Apply to cases, the case list automatically narrows to only the relevant tests for that environment. This avoids including browser-specific or OS-specific tests in runs where they do not apply.