Settings & Configuration
Configure your QAbyAI workspace
Access all settings from Settings in the sidebar. This page covers each settings section.
Account
View your profile name, email address, and team name. Team admins can edit the team name for the organization.
Users
Manage your team membership:
- Invite new users by email with a role (Admin or Member)
- Change roles — Admins can manage settings and team members; Members can create and run tests
- Remove members from the team
- Resend invitations to pending users
Only team admins can modify user settings.
Execution
Configure global test execution behavior:
- Proxy country — Select a proxy country for test runs to simulate traffic from different regions
- Interactive element whitelist — Add CSS selectors to force specific elements to be treated as interactive during test execution (useful for custom components that QAbyAI doesn't automatically detect)
For scheduling and browser configuration, see Running Tests.
Environments
Define execution environments with their own base URLs and variables. Each environment represents a deployment of your application (e.g., staging, production).
- Base URL — The root URL for your application in that environment
- Environment variables — Key-value pairs available to tests via
{{ VARIABLE_NAME }}syntax
Select an environment when running tests manually or configure a default in your test suite settings. See Running Tests for usage details.
Request Intercepts
Mock HTTP responses during test execution by defining intercept rules:
| Field | Description |
|---|---|
| URL pattern | The URL pattern to match (supports wildcards) |
| HTTP method | GET, POST, PUT, DELETE, etc. |
| Status code | Response status code to return |
| Headers | Custom response headers |
| Response body | The response body to return |
Each rule can be enabled or disabled independently. Use intercepts to:
- Mock third-party APIs that are unreliable in test environments
- Simulate error responses to test error handling
- Control API responses for deterministic test behavior
Files
Upload and manage shared files that can be used across test cases (e.g., for file upload steps):
- Upload files that are accessible to all test cases in your team
- Rename, update, or delete files as needed
- Download files to review their contents
All test cases automatically use the latest version of each file.
Extensions
Upload browser extensions (as ZIP files) that are automatically loaded during test execution:
- Upload extension ZIP files
- Enable/disable extensions without removing them
- Edit extension names and descriptions
Use browser extensions when your application under test requires specific browser add-ons to function correctly.
Persistent Variables
View and manage variables that persist across test runs within your team. Unlike session variables that reset after each test run, persistent variables retain their values.
- View current variable values (including complex JSON objects)
- Delete variables that are no longer needed
Persistent variables are set during test execution by passing 'persistent' as the third argument to setVariable:
window.setVariable('AUTH_TOKEN', token, 'persistent');
See Variables for more on how variables work.
Failure Tags
Create and manage tags for classifying test failures during triage:
- Create tags with custom names, colors, and descriptions
- Edit or delete existing tags
These tags are applied to failed test runs during Failure Triage to categorize root causes (e.g., "Network Error", "UI Change", "Test Data Issue").
API Keys
Generate API keys for programmatic access to QAbyAI:
- Create a new key with a descriptive name
- The full key is shown only once at creation — copy and store it securely
- Delete keys that are no longer needed
API keys are used for CI/CD integration and any other API-driven workflows. Include the key in the x-api-key header.
Billing & Usage
Monitor your credit consumption and account balance:
- Current balance — Credits remaining
- Monthly usage — Credit consumption trends over the last 6 months
- Breakdown by step type — See which step types consume the most credits
- Transaction history — Recent credit transactions
What's Next
- Running Tests — Select environments and browsers when executing tests
- CI/CD Integration — Use API keys in your pipeline
- Failure Triage — Apply failure tags to categorize results
- Variables — Learn how variables work in test execution
