Skip to main content
Test lists and schedules work the same as in the Portal; see Test Lists and Test Schedules. This page covers the commands.

​
Run a group of tests

--project-env <project-id>:<env> sets the environment that project’s tests run in; repeat it for each project in the list. To run only part of the list, pass --case <test-id> to testlist run. A loopback environment opens a tunnel automatically.

​
Run on a schedule

To schedule a whole project, use --target-type project --target-id <project-id>. Without --env, a project schedule runs on the project’s Default environment each time it fires; add --env staging to pin it. A test-list schedule uses the list’s environments and rejects --env; change them with testlist update --project-env. schedule create prints the estimated credits per run. Schedules need a workspace plan that includes them (exit 13 otherwise).

​
Pause, change, or check a schedule

--resume turns a paused schedule back on. schedule list shows each schedule’s environment: staging (pinned) or project default (inherits). A schedule on a loopback environment can’t reach your machine from the cloud. Its runs are recorded as blocked and not charged (failureKind: network); run the tests with test run --local <port> instead. For every flag, see Command Reference.