Test plans
A test plan groups related runs, for example everything for one release or one game integration, and holds instructions that all of its runs share. Plans are listed on the Plans & Runs tab of the Runs page.
How plans work
- Every run is created inside a plan; a run can later be moved to the root of the list.
- Plans are a flat list. A plan cannot contain other plans.
- A plan’s Test Instructions (Prompt) and attachments (up to 5,000 characters and 20 files) are added to every test case in every run of the plan. Use them for things all runs need, such as login details, the environment to use or common preconditions. See What the agent receives.
- The plan’s
Descriptionis for people and is not sent to the agent. - The Target Date and status (Draft, Active, Completed, Archived) are for planning and tracking only. They do not change how runs execute.
- Delete removes the plan but not its runs: they move to the root of the list and appear under Plans and Runs.
Launching a whole plan
Choose Launch from the plan menu to start several of its runs at once.
| Field | Description |
|---|---|
Run statuses | Which runs to launch, by their current status. By default runs that are Draft, Failed, Cancelled or Error: everything not yet run, plus anything to retry. Completed runs can be added; runs that are already Running or Queued are never launched again. |
Number of rounds | How many times each run executes all its test cases, 1 to 100. Default 1. |
On failure | Continue all rounds (default) or Stop on first failure. See Rounds. |
The preview lists the matching runs and the total number of test cases and sessions. If some runs could not start, the notification says why.
Creating, editing, launching and deleting plans requires the Tester or Manager role.