Browser Settings
Configure browser settings to ensure consistent test execution across different environments and scenarios.
Playwright Timeouts
Configure timeout settings for Playwright operations to handle different application response times. This can be overridden in each action.
Default Assertion Timeout
Maximum time to wait for an assertion to complete successfully.
- Default: 20000ms (20 seconds)
- Purpose: Ensures assertions have sufficient time to pass on slower applications
- When to adjust: Increase for applications with slower loading times or complex animations
Default Action Timeout
Maximum time to wait for an action (click, type, etc.) to complete.
- Default: 20000ms (20 seconds)
- Purpose: Prevents tests from hanging on unresponsive elements
- When to adjust: Increase for applications with heavy client-side processing
Action Delay
Add a delay between actions to make Playwright more human-like.
- Default: 300ms (0.3 seconds)
- Purpose: Prevent Playwright flakiness caused by it being too fast
- Impact: Affects both test creation and test execution
- Configuration: Can be overridden in each test suite
Action delays in browser settings affect the test recorder experience. Configure delays in individual test suites for actual test execution timing.
User Agent
Configure the browser user agent string to control how your application identifies the testing browser.
Custom User Agent Configuration
Set a custom user agent string to:
- Bypass bot detection systems
- Test user agent-specific features
- Simulate different browser types or versions
Default: STABLY-{unique-identifier}
User Agent Best Practices
- Bot Detection: Use a standard browser user agent to avoid bot detection
- Testing: Use specific user agents to test browser-specific functionality
- Monitoring: Include identifiable markers for test traffic analysis
Localization
Configure browser locale settings to test internationalization features.
Default Locale
Set the default browser locale for region-specific behavior:
- Language: Interface language and text display
- Date Formats: How dates are formatted and displayed
- Number Formats: Decimal separators and currency formatting
- Timezone: Default timezone for time-based operations
Options:
- Default (Browser Default)
- Custom locale selection (e.g., en-US, fr-FR, ja-JP)
HTTP Headers
Manage custom HTTP headers sent with all requests during test execution.
Common Use Cases
- Authentication: Add API keys or bearer tokens
- Service Tokens: Include service authentication for protected environments
- Custom Headers: Add application-specific headers
Adding Custom Headers
- Click + Add Header
- Enter header name and value
- Save configuration
Headers are applied to all requests made during test execution.
Clerk Configurations
Configure Clerk authentication settings for applications using Clerk authentication services.
Service Token Integration
Add Clerk service tokens to bypass bot detection and enable authenticated testing.
Configuration Steps
- Click + Add Configuration
- Enter your Clerk service details
- Configure token refresh settings
- Save and test configuration
Multiple Browsers
Enable testing across different browser types and versions.
Browser Support
By default, tests run in Chromium. Enable multiple browser testing to:
- Test cross-browser compatibility
- Validate browser-specific features
- Ensure consistent user experience
Supported Browsers
- Chromium: Default browser for all tests
- Firefox: Available with multiple browser mode
- Safari: Available with multiple browser mode (on macOS)
Enabling Multiple Browser Mode
Contact us to enable multiple browser testing for your workspace. This feature allows:
- Parallel execution across browser types
- Browser-specific test configurations
- Comprehensive compatibility testing
Multiple browser testing requires additional resources and may affect test execution time. Plan test suites accordingly.