Running Test Cycles and Executions

Test Cycles and Execution

Test cycles group test cases for organized testing efforts. Execute tests within cycles and record results step by step.

Creating a Test Cycle

1. Navigate to QA > Test Cycles.
2. Click Add.
3. Enter the cycle name and description.
4. Optionally assign to a folder.
5. Click Save.

Adding Test Cases to a Cycle

1. Open the test cycle.
2. Click Add Test Cases.
3. Search and select test cases from your library.
4. Click Add Selected. Each test case creates a test execution within the cycle.

Executing a Test

1. Open a test execution within the cycle.
2. Click Start to begin execution.
3. Follow each test step and record the result for each step: Pass, Fail, or Blocked.
4. Add comments or attach screenshots as evidence.
5. When all steps are complete, mark the overall execution as Pass, Fail, or Blocked.

Blocking an Execution

If prerequisites are not met, block the entire execution with a reason. This records why the test could not be run.

Linking Defects

1. When a test step fails, click Add Defect.
2. Search for an existing Bug issue or create a new one.
3. The defect is linked to the test execution for traceability.

Tracking Progress

View cycle progress showing the count and percentage of passed, failed, blocked, and not-run executions.

Closing a Cycle

When testing is complete, click Close on the test cycle. Closed cycles are preserved as a historical record.

Cloning a Cycle

Clone a test cycle to reuse the same set of test cases for a new testing effort (e.g., regression testing for the next release).

Bulk Operations

Select multiple test executions to bulk-update status. Select multiple cycles to bulk-close, clone, or delete.