Running Tests
Learn how to execute test suites, monitor progress, and analyze results in AegisRunner.
Running Tests
Once you have test suites generated from crawls or created manually, you can run them across multiple browsers to verify your website works correctly.
Plan Limits
| Plan | Test Runs/Month | Parallel Runs | Data Retention |
|---|---|---|---|
| Free | 50 | 1 | 7 days |
| Starter ($9/mo) | 500 | 2 | 30 days |
| Pro ($29/mo) | 2,500 | 5 | 90 days |
| Business ($59/mo) | 10,000 | 10 | 1 year |
Running a Test Suite
Click Test Suites in the sidebar to view all your test suites.
Use the search bar or filter by crawl session to find the suite you want to run.
Click the Run button on the suite card.
Choose which browser to run the tests in:
- Chromium - Chrome/Edge-based testing
- Firefox - Firefox browser testing
- WebKit - Safari-based testing
Click to start the test execution. You'll be taken to the runs view.
Viewing Test Runs
Navigate to Test Runs in the sidebar to see all test executions.
Run Statistics
The top of the page shows aggregate statistics:
- Total Runs - All test runs in the selected period
- Passed - Runs where all tests passed
- Failed - Runs with at least one failing test
- Running - Currently executing runs
Filtering Runs
Filter the runs list by status:
- All - Show all runs
- Passed - Only successful runs
- Failed - Only failed runs
- Running - In-progress runs
- Pending - Queued runs
Use the search bar to find runs by suite name or ID.
Run Cards
Each run card displays:
- Status Icon - Visual indicator of pass/fail/running
- Suite Name - Which test suite was executed
- Run ID - Unique identifier for the run
- Results - Count of passed, failed, and skipped tests
- Project - Which project the run belongs to
- Date - When the run was executed
- Duration - How long the run took
Test Run Details
Click on any run card to view detailed results:
Individual Test Results
See the outcome of each test in the suite:
- Passed - Test completed successfully
- Failed - Test failed with an error
- Skipped - Test was skipped (usually due to dependency failure)
Error Details
For failed tests, view:
- Error message and stack trace
- Screenshot at point of failure
- Expected vs actual values
- Steps executed before failure
Trace Files Pro+
Pro and Business plans include Playwright trace files for debugging:
- Step-by-step execution timeline
- Screenshots at each action
- Network requests
- Console logs
- DOM snapshots
Exporting Tests
Export your test suites as Playwright code:
- Go to Test Suites
- Click the Export Playwright button on a suite
- Download the generated
.spec.tsfile - Run locally or integrate into your CI/CD pipeline
Browser Considerations
| Browser | Engine | Best For |
|---|---|---|
| Chromium | Blink | Most common browser, good default choice |
| Firefox | Gecko | Testing Firefox-specific behavior |
| WebKit | WebKit | Testing Safari/iOS compatibility |
Queue Behavior
Test runs are queued based on your plan:
- Free/Starter - Runs queue and execute based on availability
- Pro - Priority queue with faster execution
- Business - No queue, immediate execution
Related Documentation
- Debugging Tests - Fix failing tests
- Scheduling Tests - Automate test runs
- Test Data Management - Configure test data
Visual Regression Mode
Enable visual regression when running tests to capture and compare screenshots:
- Toggle Enable Visual Regression in the run options
- First run captures baseline screenshots
- Subsequent runs compare against baselines
- Review diffs in the step results panel
See Visual Regression Testing for full details.
API Test Steps
Test suites can include api-request steps that test REST/GraphQL endpoints directly:
- HTTP requests (GET, POST, PUT, DELETE) without browser overhead
- Status code and response body assertions
- JSON path matching for nested response validation
- Response time thresholds for performance monitoring
See API Testing for full details.