Docs · running tests
Plans.
An optional grouping of cycles with a shared lifecycle.
A plan groups related cycles, for example every cycle belonging to a release. Plans are optional: cycles work fine without one.
- A plan is open while its rounds are in progress.
- Closing a plan cascade-closes its member cycles and freezes the rollup: the plan becomes the immutable record of that effort.
- Reopening is restricted, deliberately.
Use plans when you need one line of truth per release ("Release 2.3 testing: 4 cycles, 212 executions, 94% pass") rather than assembling it from individual cycles.