How-to

Autotest run creation

Autotest run creation ​

Autotest run creation starts worker execution: choose autotests, a verified domain, and an execution context, then start the run.

Role: a team member with write access to the project. A read-only member cannot start a run.

Prerequisites ​

  1. At least one autotest with kind CASE and status READY in the project.
  2. A verified team domain for the site under test.
  3. An execution context snapshot (protocol and environment axes). The snapshot is required; individual axes inside it may be empty - the worker applies Chromium / 1920x1080 per the rules on the execution context page.

Steps ​

  1. Open Autotest runs in the project and click Autotest run. On an empty list the button is Create first autotest run. Or check autotests in the autotest list and click Autotest run: the form opens with those autotests selected.
  2. Enter a name. It is required. The description can stay empty.
  3. Select the Starting domain (verified).
  4. Select the execution context snapshot.
  5. Choose which READY + CASE autotests to include (all, or a list). If the form was opened from checked rows on the autotest list, those autotests are already selected.
  6. If the project contains <<name>> tokens, the form shows Run parameters under that choice. One row per name: the label is run_parameter_name, the field is run_parameter_value. Fill every row. The list is the whole project (step values, repository page paths, repository element locators), not only the autotests selected above. If the project has no tokens, the block is absent.
  7. Set timeouts, threads, retries, and screenshot options as needed.
  8. Start the run.

Relative goto uses the starting host plus the protocol from the execution context (HTTP or HTTPS, default HTTPS). If a COMMON predecessor opened a team subdomain, the next relative path still joins the starting domain: for a screen on the subdomain you need a catalog page with a full URL. A screen capture is the Screenshot on failure and Result screenshot options, not a step. Breakdown: How to author autotest steps without false failures.

After you start ​

  • Open the run details to review queued autotest results. Refresh the page manually for status updates.
  • Field meanings and clone rules: Autotest run.
  • Per-autotest outcome and step report: Autotest result.

Limits and notes ​

  • Only READY + CASE autotests enter the queue. Predecessors of kind COMMON run in the same browser session before the case steps.
  • An empty Run parameters field blocks the start. The values are stored on this run. A later run asks for them again.
  • Clone starts a new run and copies the run parameter values from the source run. It does not copy old autotest results.

Version 1.5.0 · Last updated 2026-10-27

Did this page help?