Skip to main content

​
Overview

Test configuration controls how your tests execute. Supatest now uses Run Configs as reusable execution profiles that you can attach to test cases, test plans, and ad-hoc runs.

​
Video overview

​
Run Configs

A Run Config defines runtime settings such as:
  • Browsers (Chrome, Safari, Firefox, Edge)
  • One or more viewport sizes
  • Locale
  • Timezone
You can create a config once and reuse it anywhere.

​
Manage Run Configs

  1. Go to Runs
  2. Open the Run Configs tab
  3. Click Create Run Config
  4. Set name, optional description, and runtime settings
  5. Save
You can also edit and archive run configs from the same tab.
Run Configs table in Runs page (light mode)
When creating a config, you define a name, optional description, and execution settings in one form.
Create Run Config form (light mode)

​
Where to Attach Run Configs

​
Test Case Level

  1. Open a test case
  2. Open Settings
  3. In Run Configs, select one or more configs
  4. Save
Selecting multiple run configs in test case settings (light mode)

​
Test Plan Level

  1. Open or create a test plan
  2. In Run Configs, select one or more configs
  3. Save

​
Ad-hoc Run Level

  1. Go to Runs
  2. Click Create Run
  3. Select test cases
  4. Optionally select run configs for this one run
  5. Create run

​
Precedence Rules

When multiple levels are available, Supatest resolves run configs in this order:
  1. Ad-hoc Create Run selected run configs (highest priority)
  2. Test plan run configs
  3. Test case attached run configs
  4. System default config (Chrome + default viewport)

​
Runtime Expansion

A single run request can expand into multiple concrete executions. Total concrete runs are computed from:
  • selected test cases
  • run configs in effect
  • browsers per config
  • viewports per config
  • enabled scenario rows (for table-driven tests)
Example: 2 configs x (2 browsers each) x (2 viewports each) x 3 scenario rows = 24 concrete runs for one test case.

​
Other Test Settings

In test case settings, you can also configure:
  • Step timeout
  • Auto-healing
  • Table-driven tests (Scenarios)

​
Best Practices

  • Keep run configs focused by purpose (for example: Desktop Smoke, Mobile Regression).
  • Prefer attaching shared configs at the test plan level for suite-wide consistency.
  • Use ad-hoc run-level configs when you need temporary overrides.
  • Use multiple viewports in a single config to avoid creating many near-duplicate test cases.

​
Troubleshooting

​
Run Count Is Higher Than Expected

Your run likely expanded across multiple browsers/viewports and/or scenario rows. Check attached run configs and enabled scenario rows.

​
Wrong Browser or Viewport Ran

Check precedence: a run-level or plan-level config may have overridden test-level configs.

​
No Run Config Applied

If nothing is attached at run/plan/test level, Supatest uses the system default config.
  • Create a Run - Launch ad-hoc runs with run config selection
  • Test Cases - Attach run configs to individual tests
  • Test Plans - Configure plan-level run configs
  • Scenarios - Table-driven test data and scenario rows