01Cycle examples
- "v1.4 regression"
- "Sprint 23 testing"
- "Pre-launch QA for the marketing site"
A cycle is a container. It groups related runs so reporting is meaningful at the release or period level.
02Run examples (within a cycle)
- "v1.4 regression — Chrome desktop"
- "v1.4 regression — Safari mobile"
- "v1.4 regression — staging API smoke"
Each run is a specific execution against a specific environment, with a defined set of cases.
03Why both exist
Without cycles, you'd have a flat list of runs and no easy way to roll up reporting per release. Without runs, you'd have a label ("v1.4 testing") with no actual execution detail.
04Related
05Frequently asked questions
Can I have a cycle without runs?
A cycle starts empty and gets runs added over time. An empty cycle is a planned-but-not-yet-executed period.
Should I create a cycle per release?
Per release is a common pattern. So is per sprint, per environment, or per major customer demo. Match cycles to the unit of testing you actually report on.