Autotest run ​

An autotest run executes selected autotests on a verified team domain, with an execution context snapshot.

Relations ​

Rules ​

• Create options include a name, a description, the starting domain, protocol from the execution context, timeouts, threads, retries, screenshot on failure, and result screenshot. The name is required. The run page shows the name and the description as text.
• The project run list has a table, a list, cards, and a timeline. See Autotest run listing views.
• Result statuses include PASSED, FAILED, SKIPPED, ERROR.
• The fields block is named Details and starts collapsed. The results table is named Results and starts expanded. After that, this browser remembers whether each block is open.
• In the results table the autotest column shows the name. If there is no name, the identifier remains.
• Refresh on run details is manual. There is no automatic poll in the UI.
• Clone starts a new run and copies the run parameter values from the source run. It does not copy old job results.
• If a step or a catalog record uses <<name>> and that name is missing on the run, the autotest result is ERROR. That case is not retried.

Limits ​

• Navigation during the run is allowed only to hosts that match a verified domain of the team. A verified root covers its subdomains for autotest navigation.
• Device on the execution context describes the environment for people. The worker applies User-Agent and screen resolution; it does not emulate a phone profile from Device alone. Empty browser and screen axes default to Chromium and 1920x1080 - see Execution context.