Overview
Execution settings define how a test case runs; the browser, resolution, device, location, persona, environment, and advanced options. Settings can be saved per test case so your team always runs with consistent configuration.
Execution Settings Overview
Setting | Description | Default |
Browser Type | Browser engine (Chromium, Chrome, Firefox, Safari) | Chromium |
Resolution | Viewport size (e.g., 1280x720) | 1920x1080 |
Location | Browser geolocation | Paris (new) |
Locale | Browser language (e.g., en-US, fr-FR) | en-US |
Persona | Test persona to use | QA Engineer |
Environment | Target environment | Production |
Device Scale Factor | Pixel density (1, 2, 3) | 1 |
Advanced Settings
Setting | Description | Default |
Ignore HTTPS Errors | Skip HTTPS certificate validation | false |
Stealth Mode | Anti-detection / avoid bot detection | false |
Dark Theme | Enable dark mode in browser | false |
JavaScript | Enable/disable JavaScript | true |
Highlight Elements | Highlight interacted elements during execution | true |
Forced Colors | Force high-contrast color mode | none |
HTTP Credentials
Setting | Description | Default |
Username | HTTP Basic Auth username | (none) |
Password | HTTP Basic Auth password | (none) |
Note: HTTP credentials are encrypted and are only used for HTTP authentication challenges during test execution. These credentials are separate from environment-level test credentials or secrets.
Configuring Execution Settings
You can configure execution settings directly from the Test Case view. The settings panel is located above the browser display and includes:
Browser & Device settings — Select the browser type, resolution, device type, and location
Persona & Environment — Choose the persona and environment for your test run
Advanced Settings — Access additional options (HTTPS errors, stealth mode, dark mode, etc.) by expanding the "Advanced Settings" panel
HTTP Credentials — Configure HTTP Basic Auth credentials for sites that require them
A red indicator appears when your current execution settings differ from the saved team defaults. This helps you know at a glance whether you're running with:
Custom (unsaved) settings → red indicator visible
Saved team defaults → no indicator
An "Unsaved changes" alert bar may also appear to remind you that your current configuration hasn't been persisted.
Save Settings as Team Default
You can persist execution settings for a test case so that your entire team uses the same configuration by default.
How to Save
Configure the desired execution settings in the Test Case view
Click the "Save as team's default" button
What Gets Saved
All execution settings are saved for that test case, including:
Browser type, resolution, device type, and location
Persona and environment
Advanced settings (HTTPS, stealth, dark mode, etc.)
HTTP credentials (encrypted at rest)
Saved settings are team-wide — all team members see the same defaults when they open that test case.
Reset to Saved Defaults
If you've made temporary changes to the execution settings and want to revert:
Click the "Reset" button in the execution settings panel
All settings revert to the last saved team defaults
The Reset button appears whenever your current settings differ from the saved values.
Settings Merge Behavior
When a test case is executed, settings are resolved in the following priority order:
Priority | Source | Description |
1 (Highest) | UI / CSV overrides | Settings provided in the execution settings dialog or CSV native columns |
2 | Saved execution settings | The team's saved defaults for that test case |
3 (Lowest) | System defaults | Chromium, 1920x1080, Paris (new) |
Example
If a test case has saved settings with Firefox browser and 1920x1080 resolution, and in the settings modal it specifies only "Chrome" as browser:
Browser: Chrome (from settings modal override)
Resolution: 1920x1080 (from saved settings)