Clone Test Cycle

Users can create a clone of existing test cycles with their test steps.

For example, Testers need test cycles for the next release. These new test cycles may have some common field values as existing test cycles. The test cycle needs to be a copy of the existing test cycle. So they create a copy of the existing test cycle using the Clone feature.

Steps:

Clone from Test Cycle List View

1. Hover over the test cycle you want to clone. Three icons become visible now: Execute, Clone and Delete.

2. Click on the Clone icon to create a copy of the existing test cycle.

Clone from Test Cycle Detail Page

  1. Open the test cycle detail page.

  2. Click on the Clone icon at the top to create a copy of the existing test cycle.

The Clone Test Cycle pop-up opens.

You can clone test cycles in either the Current Project or in Other Project.

Current Project: Select the section to clone test cycles in the current project.

  • Select Target Folder: Select the target folder in which you want to clone the test cycle. By default, they will be cloned to “All Test Cycles”

  • Test Cycle Name: You can edit the test cycle name. By default, the “Cloned” pre-fix is added to the test cycle name.

  • Test Case filters: The test cases can be filtered based on multiple fields as displayed on the expandable filter panel. Only the filtered test cases will be copied.

Test Case Filters:

→ Execution Result

→Execution Assignee

→Components

→Environment

→Defect

→Status

→Build

→Labels

→Priority

To reset the selected values, click Reset Filter Values.

  • Clone Test Cycle with

    • All Test Case Executions: It will clone the test cycle with all executions of the test case.

    • Latest Execution: It will clone only the latest execution of the test case.

  • Mark Execution Result Of New Test Cycle as

    • Actual Execution Result: It will copy all test cases within the test cycle with their current execution status.

    • Not Executed: It will copy all the test cases within the test cycle and assign them "Not Executed" status.

  • Additional Options

    • Copy Defects: If this option is selected, it will copy the test cycle with defects associated with test cases and test steps.

    • Copy Comments: If this option is selected, it will copy the Comments entered for the test cases on the execution screen.

    • Copy Attachments: If this option is selected, it will copy the attachments added to the test cases and test steps from the execution screen.

    • Copy Execution Custom Fields: If this option is selected, it will copy the custom field values entered on the execution screen.

    • Copy with the actual result of the test step: If this option is selected, it will copy the test cycle with the actual result of the test steps under the test cases.

    • Copy Execution Custom Fields: If this option is selected, it will copy the custom field values entered on the execution screen. If you are cloning the test cycle with “Actual Result”, then the “Copy execution custom fields“ checkbox remains selected and the execution custom fields get copied by default.

Click on the Clone button to initiate the cloning process in the current project.

You can see the test cycle is cloned with the “Cloned” prefix in the selected destination folder if the name is not changed while cloning the test cycle. The test case version that is associated with the test cycle will get cloned.

 

Other Project: Select the section to clone test cycles in other projects. The association of test cases with test cycles will be carried forward from the source project. The test cases of the source project will be reused in the target project with the Execution Result as Not Executed.

  • Select Target Project: Select the target project to clone the selected test cycles in that project.

  • Select Target Folder: Select the target folder in which you want to clone the test cycles. By default, the test cycles will be cloned to “All Test Cycles”.

  • Select Target Fix Version

  • Select Target Sprint

  • Test Cycle Name: You can edit the test cycle name. By default, the “Cloned” pre-fix is added to the test cycle name.

  • Test Case filters: The test cases can be filtered based on multiple fields as displayed on the expandable filter panel. Only the filtered test cases will be copied.

Test Case Filters:

→ Execution Result

→Execution Assignee

→Components

→Environment

→Defect

→Status

→Build

→Labels

→Priority

To reset the selected values, click Reset Filter Values.

  • Clone Test Cycle either with All Test Case Executions or Latest Test Case Execution.

  • Test Cycles will be cloned in the target project with the Execution Result marked as Not Executed.

  • Additional Options: Select from the following options to copy test cycle and test execution with:

    • Create Meta Data: It will create meta data like labels, components, status, priority and custom fields in target project if those values do not exist in the target project. Hence, if you want to copy these fields from the source project to the current project, make sure you select the Create Meta Data option on the screen. In case of custom fields, the fields will be copied in the Custom Fields section of Project Configuration and will also be copied in test cycle, test execution with filled values.

    • Copy Attachments: It will clone test cycles with attachments added to them.

    • Copy Comments: It will clone test cycles with comments added to them.

Click on the Clone button to initiate the cloning process in the target project.

You can see the test cycle is cloned with the “Cloned” prefix in the selected destination folder under the selected target project if the name is not changed while cloning the test cycle.