Running Tests
Execute tests manually, on a schedule, or via CI/CD
Running a Single Test
From any test case page:
- Click Run in the top-right
- Select the environment to run against
- Choose the browser (Chromium, Firefox, or WebKit)
- Click Execute
The test begins immediately. You can watch it execute in real-time with live screenshots and step-by-step progress. Results appear on the test run detail page once complete.
Running a Test Suite
From a test suite page:
- Click Run Suite
- The suite runs all included test cases against the configured environment and browser
Each test case in the suite gets its own test run. The overall suite run tracks aggregate results — how many passed, failed, or are still running.
See Test Suites for how to create and configure suites.
Environments
Environments let you run the same tests against different deployments of your application (staging, production, custom).
Each environment defines:
- Base URL — The root URL for your application in that environment
- Variables — Environment-specific values (API keys, feature flags, credentials)
Configure environments in Settings > Environments. When running a test, the environment's base URL is used for navigation and its variables are available via {{ VARIABLE_NAME }} syntax.
Browser Selection
QAbyAI supports three browser engines:
| Browser | Engine | Use case |
|---|---|---|
| Chrome | Chromium | Default, most common |
| Firefox | Gecko | Cross-browser verification |
| Safari | WebKit | Apple ecosystem testing |
Select the browser when triggering a manual run or configure a default in your test suite settings.
Scheduling Runs
Test suites can be scheduled to run automatically:
- Open a test suite
- Go to suite settings
- Set a cron schedule (e.g., daily at 9am, hourly, weekly)
- Select the environment and browser
Scheduled runs appear in the Runs page with a "Scheduler" trigger type. Set up email notifications to get alerted when scheduled runs complete or fail.
Execution Settings
Configure global execution behavior in Settings > Execution:
- Proxy country — Route test traffic through a specific country's proxy for geo-specific testing
- Interactive element whitelist — Add CSS selectors to force custom elements to be treated as interactive
See Settings & Configuration for full details.
What's Next
- Test Runs & Suite Runs — View and analyze results
- CI/CD Integration — Trigger tests from your deployment pipeline
- Failure Triage — Categorize and track failures