Settings
AutoRunner's settings page is Run Profiles — reusable recipes for how test plans run: where, how fast, and with which data. That is the whole page; it has no other tabs.
Two things that used to live here have moved:
| Was | Now |
|---|---|
| Source tab | The Sources page |
| Notification tab | The platform-wide Notification Settings screen |
Older /autorunner/settings/<section> links all still resolve, and land on this page.
Run Profiles
This tab has three sections.
Project Execution Defaults
Defaults for every new run configuration. An individual profile can override them, up to the limits set here.
Select Edit to see two panels.
| Panel | Fields |
|---|---|
| Limits (cannot be exceeded) | Max Parallel, Max Run Timeout, Max Scenario Timeout |
| Defaults (can be overridden) | Default Parallel, Default Run Timeout, Default Scenario Timeout |
Two switches complete the section: Screenshot on Fail and Screenshot on Pass.
Quality Gate
Set a minimum pass rate. Runs below the threshold are marked as failing the quality gate.
- Enable Quality Gate turns the gate on, starting at 80%.
- Pass rate threshold sets the percentage.
A failed quality gate is reported on the run and in reports.
It does not stop the run, block a later run, or block a merge or deployment.
To act on a gate result, read qualityGatePassed from the API in your pipeline — see CI/CD Integration.
Run Profiles
Saved configurations describing how tests are executed. Select New Profile to create one, or use a card's menu for Edit, Clone, Set as Default, and Delete.
The profile form contains:
| Field | Notes |
|---|---|
| Name | For example, "Production Desktop Test" |
| Description | Optional |
| Engine | A specific engine, or no specific engine |
| Execution Targets | At least one target is required |
| Environment | An environment profile, or project defaults only |
| Runtime Variables | Key and value pairs applied for this profile |
Under Shared Capabilities:
- Headless Mode — run browsers without a visible UI.
- Window Size — the browser viewport.
- A Selenium hub URL, when you point at your own grid.
Under Advanced Settings:
- Parallel Execution — how many scenarios run at once.
- Run Timeout and Scenario Timeout.
- Retry on Failure and the retry count.
- Screenshot on Pass and Screenshot on Fail.
Profiles with an API execution target also expose Newman/Postman Parameters: Iterations, Request Timeout, Total Timeout, Script Timeout, Delay Between, Allow Insecure SSL, and Ignore Redirects.
Under Notifications, a profile either follows the workspace default or sets its own Recipient Type — None, Send to Me, Admin & Managers, or Everyone in Project — plus an explicit Recipients email list.
Next Steps
- Sources — Connect a source and manage its repository or collection
- Notification Settings — Per-event notification control and templates
- Test Datas — Environments and variables the profiles select
- Test Plans — Assign a default run profile to a plan
