Test Configuration

​

Overview

​

Configuration Options

​

Browser Settings

1. Open test settings
2. Select Browser dropdown
3. Choose your browser
4. Save changes

​

Viewport Configuration

1. Open test settings
2. Find Viewport section
3. Select preset or enter custom dimensions
4. Save changes

​

Timeout Settings

1. Open test settings
2. Find Timeouts section
3. Enter values in seconds/minutes
4. Save changes

• Slow network environments
• Complex page loads
• Long API responses
• Heavy JavaScript applications

​

Auto-Healing

1. Step fails due to locator not found
2. System tries fallback locators
3. If fallbacks fail, AI analyzes the page
4. AI finds correct element and continues
5. Healing suggestion saved for review

​

Run Configuration

​

Applying Settings

​

Test-Level Settings

1. Open the test case
2. Click Settings tab or gear icon
3. Modify settings
4. Save changes

​

Environment-Level Settings

1. Go to Environments
2. Select an environment
3. Configure default settings
4. Tests inherit these when run in this environment

​

Organization Settings

1. Go to Settings > Organization
2. Configure default test settings
3. All new tests inherit these defaults

​

Settings Priority

1. Test-level (highest priority)
2. Environment-level
3. Organization-level (lowest priority)

​

Common Configurations

​

Mobile Testing

Viewport: 375 x 667 (Mobile)
Browser: Chromium
User Agent: Mobile Chrome

​

Slow Application Testing

Step Timeout: 30 seconds
Navigation Timeout: 60 seconds
Test Timeout: 10 minutes

​

Cross-Browser Testing

Run 1: Chromium
Run 2: Firefox
Run 3: WebKit

​

CI/CD Optimized

Headless: Yes
Video: On failure only
Screenshots: On failure only
Trace: Disabled

​

Debug Configuration

Headless: No
Video: Always
Screenshots: Always
Trace: Enabled
Timeout: Extended

​

Video Recording

​

Recording Options

​

Accessing Recordings

1. Open the test case and go to the Last Run Report tab (or open a specific run from the Runs tab)
2. Click the Video sub-tab
3. Play or download recording

​

Video Best Practices

• Use “On failure” for CI to save storage
• Use “Always” for debugging sessions
• Videos help diagnose visual/timing issues

​

Screenshot Capture

​

Screenshot Options

​

Viewing Screenshots

1. Open the test case and go to the Last Run Report tab (or open a specific run from the Runs tab)
2. Click the Screenshots sub-tab
3. Navigate step-by-step images

​

Screenshot Tips

• Step screenshots help identify where issues started
• Compare screenshots across runs
• Use for visual regression checks

​

Trace Files

​

What Traces Capture

• Network requests and responses
• DOM snapshots at each action
• Console messages
• Action timing details
• Browser events

​

Using Traces

1. Open the test case and go to the Last Run Report tab (or open a specific run from the Runs tab)
2. Click the Trace sub-tab
3. Open in Trace Viewer
4. Navigate timeline and inspect actions

​

When to Use Traces

• Debugging intermittent failures
• Investigating timing issues
• Analyzing network behavior
• Understanding step execution

​

Advanced Settings

​

Custom Headers

Headers:
  - Authorization: Bearer {{ env.TOKEN }}
  - X-Custom-Header: value

​

Geolocation

Geolocation:
  Latitude: 37.7749
  Longitude: -122.4194

​

Permissions

Permissions:
  - geolocation
  - notifications
  - camera

​

Best Practices

​

Environment-Specific Settings

• Different timeouts per environment (staging vs prod)
• Environment-specific headers
• Browser variations

​

Optimize for CI

• Enable headless mode
• Record video on failure only
• Disable traces unless debugging
• Set appropriate timeouts

​

Debug Settings

• Disable headless
• Enable all recordings
• Enable trace
• Increase timeouts

​

Troubleshooting

​

Tests Timing Out

1. Check which step times out
2. Increase step or navigation timeout
3. Verify element loads correctly
4. Check for slow network/API calls

​

Video Not Recording

1. Verify video setting is enabled
2. Check storage quota
3. Ensure test completed (not cancelled)
4. Wait for video processing

​

Screenshots Missing

1. Verify screenshot setting is enabled
2. Check if step actually executed
3. Ensure run completed normally
4. Check for execution errors

​

Trace Not Available

1. Verify trace setting was enabled before run
2. Check if run completed
3. Re-run with trace enabled

​

Related

• Folders & Organization - Organize your tests
• Environments - Environment-specific settings
• Debugging Tests - Use videos, screenshots, traces
• Run History - View past executions