Introduction

Apart from cloning single test cycles, users can clone multiple test cycles in bulk at once. The feature is helpful to testing teams when the same set of test cycles are required in every release testing. The team can pick required test cycles and clone them all at once either in the current project or in other project.

Note: Maximum 20 test cycles can be cloned at a time.

Steps

1. On the folder tree at the left, select the source folder wherein the test cycles lie.

2. Select test cycles that you want to clone.

Selection of Multiple entities at a time: To select entities within a range on the current page, select the first entity’s check box and then select the last entity’s check box and simultaneously hold the SHIFT key of the keyboard. All the entities between these two entities will get auto-selected.

• Select All:

→ Select all records on the current page: Clicking on the check box in the column header selects all the records on the current page only. An alternate way is to open the check box drop-down and select Current Page.

→ Select all records across all pages: Open the check box drop-down and select Across All Pages option.

Once you select the test cycles that you want to clone, the options for bulk operation become visible on the screen.

3. Click on the Clone option.

Open

The Bulk Clone Test Cycles screen opens.

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

Clone Test Cycles in Current 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 cycles. By default, test cycles will be cloned to “All Test Cycles” (i.e. at root folder level).

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

• Mark Execution Result as either as “Not Executed” or copy same Actual Execution Result.

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

  • Copy Defects

  • Copy Attachments

  • Copy Comments

  • Copy Execution Custom Fields: If this option is selected, it will copy the custom field values entered on the execution screen. If Actual Execution Result is selected in the option above to mark the execution result, then it will force copy the execution custom fields.

  • Copy with actual result of test steps

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

Open

You can see the test cycles are cloned with “Cloned” prefix in the selected destination folder. The test case version that is associated with the test cycle will get cloned.

Clone Test Cycles in Other Project

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” (i.e. at root folder level of the other project).

• Select Target Fix Version: Select the Fix Version from the target project.

• Select Target Sprint: Select the Sprint from the target project.

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

• Mark Execution Result as:

  • Not Executed: If this option is selected, the test cycles will be cloned in the target project with the Execution Result marked as “Not Executed”.

  • Actual Execution Result: If this option is selected, the test cycles will be cloned and the execution results will be marked according to the execution results in the source test cycle. The “Create Meta Data” option under the Additional Options section will get automatically selected as soon as you select the Actual Execution Result option. All mandatory as well as optional custom field values will get copied.

  • Note: If mandatory custom fields -

    • exist in source project and not in destination project, the custom fields will not be created in the destination project

    • do not exist in source project and exist in destination project, the execution will not be created in the destination project.

• 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 cycles are cloned in the selected destination folder under the selected target project.