Element reference
Autotest
Autotest
An autotest is a check that a program executes. Steps use Playwright action names and live in the project.
Relations
| Related element | How it connects |
|---|---|
| Project | Required owner |
| Autotest step | Ordered steps |
| Test account | Optional bind on kind CASE only |
| COMMON predecessor | Explicit list of READY + COMMON autotests in the same project |
| Autotest result | Created when the autotest is included in a run |
| Tag | Optional labels on the card and in the listing Tags column |
Enumerations
Kind
| Value | Meaning |
|---|---|
CASE | Scenario that starts as its own job in a run |
COMMON | Setup. Does not start as its own job. Steps run only as an explicit predecessor of another autotest in the same project |
There is no kind named SHARED, SETUP, or SCENARIO.
Status
| Value | Meaning |
|---|---|
PENDING | Not ready |
READY | Can enter a run when kind is CASE |
DISABLED | Excluded from runs |
Only READY + kind CASE enter a run (all such autotests, or a list you select).
Rules
- Bind a test account on the
CASE, not onCOMMON. - A
COMMONstep may still use value sourceTEST_ACCOUNT(loginorpassword). The value comes from the account of theCASEin the queue. - If the
CASEhas no account and a step asks forTEST_ACCOUNT, the run fails. It does not send an empty string. - Predecessors on an autotest card: list
READY+COMMONautotests in this project, in order. In the UI the block is Pre autotest cases. They run first in the same browser session. Nested predecessors on thoseCOMMONcards are not expanded. - In the autotest listing, Kind (
CASE/COMMON) is editable like Status. Tags shows tags attached to the autotest.
Limits
- Before a run you need a verified team domain and an execution context snapshot. See Autotest run creation. Axes inside the snapshot may be empty: the worker applies Chromium and 1920x1080 per the rules on the execution context page.
localhostand similar reserved hosts are not accepted as starting domains.
Did this page help?