Test Cycles

Test Cycles represent specific execution rounds or testing phases, such as "v2.0 Release Testing" or "Sprint 5 Regression." Cycles contain Test Case Executions and can be populated from manual selection, collections, or entire folders. They track overall progress and aggregate pass/fail metrics across all executions.

Test Cycle workflow is straightforward, when the Test Set has been prepared, it can be marked for execution. When executions progress, status changes automatically.

Overview

The Overview tab stands from different cards:

• The Top bar shows
  • Test player, where test cases can be executed
  • shows statistics about the executions results
• Main card contains the main data
• Details shows main attributes

Planning

Here you can assign testers to executable test cases, or add new test cases, collections, requirements.

If you need inspiration on creating test cycles, check our suggestions here:

Create cycles 101

All Cases

The Source column indicates where the testcase comes from. Search and finalize your executables here.

Executions

Sneak peak about the execution progress of a cycle. Not as deep as reporting, but cycles can be scanned quickly here.

Links

Test cases can be linked to

• Requirements
• Other Test Cycles
• Jira Work items