Copy or clone test plans, test suites, and test cases

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019

Several tools support copy, clone, or import operations of test items such as test plans, test suites, and test cases. Test cases describe the steps to take to run a test and validate a feature implementation or bug fix. Test suites group test cases, and optionally other test suites, into a particular order. Test plans define a collection of test suites to run for a particular iteration or release.

Each test case is designed to confirm a specific behavior. Test cases might belong to one or more test suites, however test suites can belong to one and only one test plan.

In general, you should create a test plan for every major project milestone. Copy, clone, or import operations of test items support the following scenarios.

• Define a test plan for a new sprint or release based on an existing test plan
• Import test suites from one test plan to another test plan within the same or different project
• Copy test cases for use in different test suites and test plans
• Share test objects across projects
• Move test objects from one project to another, possibly to support consolidating projects into a single project

For more information, see Overview of test objects and terms.

Prerequisites

You must have the following permissions and access levels:

• Basic access or higher and permissions to view work items under the corresponding Area Path. For more information, see Add users to a project or team.
• Basic + Test Plans access level to add test plans and test suites, delete test artifacts, and define test configurations. Or, have one of the following Visual Studio subscriptions:
  • Enterprise
  • Test Professional
  • MSDN Platforms
• You must have the following permissions:to add or edit test-related artifacts,
  • Edit work items in this node permission set to Allow under the corresponding Area Path, to add or modify test plans, test suites, test cases, or other test-based work item types.
  • Manage test plans permission set to Allow under the corresponding Area Path, to modify test plan properties such as build and test settings,.
  • Manage test suites permission set to Allow under the corresponding Area Path, to create and delete test suites, add, and remove test cases from test suites, change test configurations associated with test suites, and modify a test suite hierarchy (move a test suite).

For more information, see Manual test access and permissions.

Work with the TCM command-line tool

To use the TCM command-line tool, you must have the following items in place:

• Installed Visual Studio 2017 Professional or earlier version. You access TCM from the command prompt and the following directories:

  • %programfiles(x86)%\Microsoft Visual Studio\2017\Professional\Common7\IDE
  • %programfiles(x86)%\Microsoft Visual Studio\2017\Enterprise\Common7\IDE
  • %programfiles(x86)%\Microsoft Visual Studio 14.0\Common7\IDE

• To run a TCM command, specify the /collection and /teamproject parameters, and /login as needed.

  Parameter	Description
  /collection:CollectionURL	Required. Specifies the URI of the team project collection. The format for the URI is as follows: - For Azure DevOps Services: http://dev.azure.com/OrganizationName - For Azure DevOps Server: http://ServerName:Port/VirtualDirectoryName/CollectionName. If no virtual directory is used, then the format for the URI is as follows:http://ServerName:Port/CollectionName.
  /teamproject:project	Required. The name of the project that contains the test objects you want to clone or import automated tests into.
  /login:username,[password]	Optional. Specifies the name and password of a valid Azure DevOps user and who has permissions to run the command. Use this option if your Windows credentials don't have the appropriate permissions, or you're using basic authentication, or you're not connected to a domain.

• You must be a valid member of one or more projects that you want to access and have the required permissions based on the commands you run. For more information, see Manual test access and permissions.

• You must have the same access levels required to add test plans and test suites to clone or import test objects.

Supported copy, clone, and import tools

Depending on the Azure DevOps version you use, you can use the clients or tools listed in the following table to copy, clone, or import test plans, test suites, or test cases.

Client/tool

Test Plans

Test Suites

Test Cases

---

Web portal ¹

✔️ Copy

✔️ Import

✔️ Copy ✔️ Bulk export/import

Web portal (Grid)

✔️ Copy and paste

Work item form

✔️ Copy

TCM CLI ²

✔️ Clone

✔️ Clone

✔️ Import automated

REST API ³

✔️ Clone

✔️ Clone

Note

1. With the release of Azure DevOps Server 2020, the web portal for Azure Test Plans was significantly updated. Many new features were added to support copy, clone, import, and export. For an overview, see Navigate Test Plans.
2. The Test Case Management (TCM) command-line tool is installed when you install Visual Studio 2017 or earlier versions. Examples provided in this article reflect the options available with the Visual Studio 2017 version. Earlier versions may support fewer options. For details, see Work with the TCM command-line tool.
3. REST API commands to support cloning of test plans and test suites were added with version 5.0, corresponding with Azure DevOps 2019.

List test plans or test suites

When you perform copy, clone, or import operations related to test plans or test suites, it’s essential to have access to their unique ID. This identifier allows you to precisely target the specific plan or suite you want to work with. By knowing the assigned ID, you can streamline your testing processes and ensure accurate replication or transfer of test-related data.

Browser

Do the following steps to generate a list of test plans, test suites, or other test objects.

1. Select Boards > Queries, from your project.
2. Enter the parameter, Work Item Type=Test Plan in your query Editor. You can list all test plans defined for the team project.
3. Enter a check in the Query across projects checkbox. The query lists all test plans defined for all projects. For more information, see Define a work item query.
4. Run the query.

Tip

While test plans, test suites, and test cases are related to each other, you can't view the relationships through a work item query. Link types don't link test plans, test suites, and test cases. Only shared steps and shared parameters link to test cases. Also, test cases link to user stories or other work items that they test.

TCM CLI

TCM supports listing of test plans and test suites. Lists specify the work ID for each test plan or test suite. This ID is the same as a plan ID or suite ID.

List test plans | List test suites

List test plans

Use tcm plans /list to determine the ID for a test plan. The ID corresponds to the work item ID defined when the test plan was created.

tcm plans /list [/planid:id  |  /querytext:query] /collection:teamprojectcollectionurl
           /teamproject:project [/login:username,[password]]

Parameter	Description
/querytext:query	Optional. Specifies the query to use to list a subset of test plans.

For descriptions of /collection, /teamproject and /login parameters, see Work with the TCM command-line tool.

Example

The following command lists the test plans defined for the Fabrikam Fiber project hosted in the fabrikamprime organization. The ID and Name corresponds to the work item ID and Title defined for the test plan. For example, test plan 86 is titled Hello World Test.

tcm plans /list /collection:https://dev.azure.com/fabrikamprime /teamproject:"Fabrikam Fiber"

Id        Name
------***----------------------------------------------------------------
66        Sprint 1
72        All sprints
77        Sprint 2
86        Hello World Test

List test suites

Use tcm suites /list to list the test suites with their work item IDs. When no optional parameters are specified, all test suites are listed for the team project.

tcm suites /list [/planid:id  |  /querytext:query] /collection:teamprojectcollectionurl
           /teamproject:project [/login:username,[password]]

Parameter	Description
/planid:id	Optional. Specifies the ID of the plan to reference the test suites to list.
/querytext:query	Optional. Specifies the query to use to list a subset of test suites.

For descriptions of /collection, /teamproject and /login parameters, see Work with the TCM command-line tool.

Example

The following command lists the test suites defined for the Fabrikam Fiber project hosted in the fabrikamprime organization. The ID corresponds to the work item ID defined for the test suite. Under the Name column, the first entry indicates the test plan that the test suite is defined under. Following the -> (arrow) is the Title of the test suite or the Title of a parent test suite. For example, test suite 75, Sub Suite 01, is a subtest suite of Suite 01 defined for the All sprints test plan.

tcm suites /list /collection:https://dev.azure.com/fabrikamprime /teamproject:"Fabrikam Fiber" 

Id        Name
------***----------------------------------------------------------------
67        Sprint 1
68        Sprint 1 -> 33 : Change initial view
69        Sprint 1 -> 34 : Welcome back page
70        Sprint 1 -> 43 : Cancel order form
73        All sprints
74        All sprints -> Suite 01
75        All sprints -> Suite 01 -> Sub Suite 01
78        Sprint 2
87        Hello World Test

Copy or clone test plans

When you create a new test plan per sprint or release, a helpful approach is to clone the test plan from the prior cycle. With minimal adjustments, the copied test plan becomes well-suited for the new cycle. This practice streamlines the planning process and ensures consistency across iterations.

Cloning proves especially useful when you need to branch your application into two versions. After cloning, you can modify tests independently for each version without impacting the other. It’s an efficient way to manage testing efforts while maintaining separation between different application variants.

Browser

1. Select Test Plans > Test plans, from your project.

2. Choose the test plan you want to copy from the Mine or All page.

3. Select More actions > Copy test plan. This option lets you copy or clone test plans within a project.

   

4. Specify the name of the new test plan, and select an Area Path and Iteration Path for the plan.

   

   • Choose one or the other radio-buttons based on the following guidance:
     • Reference existing test cases: Choose this option when you plan to merge the two branches eventually. In this case, keep the same requirements for functionality that is already implemented and tested.
     • Duplicate existing test cases: Choose this option when you want to make new user stories or requirements maintained separately. If you plan to diverge into two similar but separate applications, you might want to change the user stories of one without changing the stories of the other. Choosing this option creates an independent set of requirements for the new test cases.

   If you duplicate existing test cases, the copied test cases get assigned the Area Path and Iteration Path specified for the cloned test plan.

   For more information, see About area and iteration (sprint) paths.

   The page refreshes to display the newly copied test plan.

   

5. Update any query-based suites that you copied to use the new area and iteration paths.

6. Specify a build in the destination test plan if you cloned automated test cases.

TCM CLI

You can use the TCM command-line tool to clone a test plan to the same or different project, and to track the status of the clone operation.

List test plans | Clone a test plan | Track test plan clone status

Clone a test plan

Use tcm plans /clone to initiate a cloning operation of all test cases from one test suite to a different destination suite within the same project. The destination suite must be defined and exist in a different plan. All contained suites and test cases are cloned. The command might return an operation ID that you can use to track the status and completion of the clone operation. When the clone operation completes quickly, no operation ID is returned.

tcm plans /clone /sourceplanid:id /destinationplanname:name
          [/overridefield:name=value [/overridefield:name=value ...]]
          [/sourcesuiteids:suiteid1,[suiteid2,...]]
          /collection:teamprojectcollectionurl /teamproject:project
          [/login:username,[password]]
          [/clonerequirements]
          [/clonechildren]

The /clone /sourceplanid /destinationplanname creates a new plan. If you specify /sourcesuiteids, the command initiates a clone operation to clone the test cases to the new plan. The command returns an operation ID that can be used to track status and completion of the clone operation.

Parameter	Description
/sourceplanid:id	Required. Specifies the ID of the plan to be copied, and the ID of the suite into which the new copy gets added. If you want to copy a whole test plan, use the ID of the suite at the root of the test plan. The ID of a suite is displayed in the details pane when you select it in the test plan. You can also get a list of suites by using tcm suites /list.
/destinationplanname:name	Specifies the name of the plan into which the cloned test plan gets copied.
/overridefield:name=value /overridefield:name=value	Optional. Specify to change the value of a field in each cloned work item. Specify multiple occurrences of this parameter to change as many fields as you want. This option is required when you clone a test suite to a different project.
/sourcesuiteids:suiteid1,[suiteid2,...	Optional. Specifies source test suites within the test plan to copy.
/clonerequirements	Optional. Specifies to clone requirements category work items that are attached to requirements-based test suites. If you omit this parameter, requirements-based test suites are converted to static suites.
/clonechildren	Optional. Specify to clone all child suites of the suites provided.
/clonerequirements	Optional. Specify this switch to clone a requirement-based suite to a destination requirement-based suite. By default, a requirement-based test suite is cloned to a destination static test suite. Can only specify this option when /sourcesuiteids is provided.

For descriptions of /collection, /teamproject and /login parameters, see Work with the TCM command-line tool.

Example

The following example clones test plan 66 to a new test plan titled Test plan, Release 3, which is then assigned the ID 118.

tcm plans /clone /sourceplanid:66 /destinationplanname:"Test plan, Release 3" /overridefield:"Iteration Path"="Fabrikam Fiber\Release 3" /overridefield:"Area Path"="Fabrikam Fiber\Web" /collection:https://dev.azure.com/fabrikamprime /teamproject:"Fabrikam Fiber"
Plan created with ID: 118

Clone operation is complete.

Track the status of the test plan clone operation

Use tcm plans /clone /status to retrieve the status of the clone operation made with tcm suites /clone. Test suites that contain a large number of test cases can take a considerable time to clone.

tcm plans /clone
           /status:cloneoperationid
           /collection:teamprojectcollectionurl /teamproject:project
           [/login:username,[password]]

Parameter	Description
/status:cloneoperationid	Required. Specifies the ID of the clone operation returned when tcm plans /clone executes.

For descriptions of /collection, /teamproject and /login parameters, see Work with the TCM command-line tool.

Import or clone test suites

When you're creating the test plan for a new sprint, you often want to repeat some of the tests from the previous sprints, to make sure that the functionality you already implemented still works.

Note

• When you import (Web) or clone (TCM) a test suite to a new project, the new suite contains copies of all test cases in the source suite. However, it doesn't retain any historical data like the previous test runs, related bugs, old results.
• Shared steps referenced by the test cases are also cloned and created in the destination project.
• You can't clone test cases from and to the same test plan, even into a different suite. To accomplish this scenario, you must first move the test cases to a different, temporary test plan. Then, use the temporary test plan as the source plan and clone the test cases back to the source test plan by putting the ID into the destination test plan place. Shared steps present in the test cases are also duplicated in this process.

When you're working with Azure Test Plans, you can import a test suite from one test plan into another test plan within the current project. It doesn't matter whether the test plans are within the same project. This process involves copying or cloning the test suite, resulting in the creation of a new test suite. Additionally, any subtest suites also get duplicated. The test cases referenced by the test suites don't duplicate; instead, they get referenced by the cloned test suites.

You can use tcm suites /list to list all test suites defined for a project.

To use the same test cases in different suites and plans, copy and paste test cases using the Grid view.

Browser

1. Select Test Plans > Test plans.

2. Choose the test plan where you want to import a test suite from the Mine or All page.

3. Select More actions > Copy test plan. This option lets you copy or clone test plans within a project.

   

4. In the opened dialog, select the project if the test plan resides within a different project. Otherwise, enter the Test Plan Name or ID and Test Suite Name or ID. You can also select the name or ID from the dropdown menus.

5. Create the import. You can only import one suite from a test plan at a time.

   

   The following message displays:

   

6. When the import operation completes, the following message displays. Select Refresh to refresh your browser.

   

   The newly added test suite then displays.

   

TCM CLI

You can use the TCM command-line tool to clone a test plan to the same or different project, and to track the status of the clone operation.

List test suites | Clone a test suite | Track test suite clone status

Clone a test suite

Use tcm suites /clone to initiate a cloning operation of all test cases from one test suite to a different destination suite within the same project by default. The destination suite must be defined and exist in a different plan. All contained suites and test cases are cloned. The command returns an operation ID that you can use to track the status and completion of the clone operation.

The following options provide support for optional clone operations:

• /destinationteamproject: Clone a suite to a different project.
• /destinationworkitemtype: Specify the work item type to use when cloning the test cases. Specify this option when cloning test cases to a custom work item type.
• /overridefield: Override the values for select fields, such as the Area Path and Iteration Path fields, which is required when cloning to a different project. Or override the value of other fields to distinguish cloned test cases from the original.
• /clonerequirements: Specify this switch to clone a requirement-based suite to a destination requirement-based suite.

tcm suites /clone
           /suiteid:id /destinationsuiteid:id
           [/overridefield:name=value [/overridefield:name=value ...]]
           [/destinationteamproject:projectname]
           [/destinationworkitemtype:workitemtype]
           /collection:teamprojectcollectionurl /teamproject:project
           [/login:username,[password]] [/clonerequirements]

Parameter	Description
/suiteid:id	Specifies the ID of the suite to be copied, and the ID of the suite into which the new copy gets added. If you want to copy a whole test plan, use the ID of the suite at the root of the test plan. The ID of a suite is displayed in the details pane when you select it in the test plan. You can also get a list of suites by using tcm suites /list.
/overridefield:name=value /overridefield:name=value	Optional. Specify to change the value of a field in each cloned work item. Specify multiple occurrences of this parameter to change as many fields as you want. This option is required when you clone a test suite to a different project.
/destinationsuiteid:id	Specifies the ID of the suite into which the new copy gets added. If you want to copy a whole test plan, use the ID of the suite at the root of the test plan. The ID of a suite is displayed in the details pane when you select it in the test plan. You can also get a list of suites by using tcm suites /list.
/destinationteamproject:projectname	Optional. Specify when you want to clone the test suite to a different project but in the same organization or project collection. When specified, you must specify override field values for the Area Path and Iteration Path fields.
/destinationworkitemtype:workitemtype	Optional. Specify when you want to clone the test suite to a different work item type in the destination project.
/clonerequirements	Optional. Specify this switch to clone a requirement-based suite to a destination requirement-based suite. By default, a requirement-based test suite is cloned to a destination static test suite.

For descriptions of /collection, /teamproject and /login parameters, see Work with the TCM command-line tool.

Understand what gets cloned

When you clone a test suite, the following objects are copied from the source test plan to the destination test plan.

Test plan object	Notes
Test case	Each new test case retains its shared steps. A link is defined between the source and new test cases. The new test cases don't have test runs, bugs, test results, or build information.
Shared steps	Shared steps referenced by cloned test cases are copied.
Test suite	Test suites that are copied retain the following data: <br<br- Names and hierarchical structure of the test suites<br- Order of the test cases<br- Assigned testers<br- Configurations
Recordings	Action recordings linked from a cloned test case are copied.
Links and Attachments	All links and attachments get copied for all test items that are copied.
Test configuration	The test configuration defined for the source test plan is copied over and applied to the destination test plan.

The following test information isn't copied:

• Test settings: The test setting for the source test plan isn't copied. Instead, the test settings for the destination test plan are applied.
• Test results and test runs: No test results are copied. Because test runs are applicable only to the source test plan, they aren't copied.

When /clonerequirements is specified and Requirements-based test suites are copied:

• The Requirements-based test suites get copied and linked to a new copy of the requirement work item.
• Requirements work items (product backlog items or user stories) that are associated with a cloned requirements-based suite get cloned.
• Bug work items get cloned in a project that uses the Scrum process template, or any project in which the Bug work item type is in the Requirements work item category. Otherwise, bugs aren't cloned.

When /clonerequirements in't specified and Requirements-based test suites get copied:

• Requirements-based test suites convert to static test suites in the destination test plan.
• Cloned test cases are referenced under the static test suite.
• Cloned test cases don't include links to their original requirements work items.

Example

The following example illustrates cloning test suite 97 defined for the Fabrikam Fiber project to the Fabrikam Git project. Because the test suite contained a query-based suite, a warning message is listed to review and revise the respective query in the source and destination test suites.

tcm suites /clone /collection:https://dev.azure.com/fabrikamprime /teamproject:"Fabrikam Fiber" /destinationteamproject:"Fabrikam Git" /suiteid:97 /destinationsuiteid:104 /overridefield:"Iteration Path"="Fabrikam Git" /overridefield:"Area Path"="Fabrikam Git"

Started clone operation with id 4.
Use /status:4 to get progress and completion information of the operation.
Warning: You have cloned the following query based suites as part of this clone operation. You are advised to fix their respective queries in the source and destination suites, after the clone operation completes.
1. Sprint 3 -> Sprint 3 query-based suite

Track the status of the test suite clone operation

Use tcm suites /clone /status to retrieve the status of the clone operation made with tcm suites /clone. Test suites that contain a large number of test cases can take a considerable time to clone.

tcm suites /clone
           /status:cloneoperationid
           /collection:teamprojectcollectionurl /teamproject:project
           [/login:username,[password]]

Parameter	Description
/status:cloneoperationid	Required. Specifies the ID of the clone operation returned when tcm suites /clone executes.

For descriptions of /collection, /teamproject and /login parameters, see Work with the TCM command-line tool.

Example

tcm suites /clone /status:4 /collection:https://dev.azure.com/fabrikamprime /teamproject:"Fabrikam Fiber"

Clone operation 4 has succeeded. Summary information:
Started on:           10-Nov-21 5:00:28 PM
Started by:           Jamal Hartnett
Source suite id:      97
Destination suite id: 114
Test cases cloned:    9
Shared steps cloned:  0
Requirements cloned:  0
Completed on:         10-Nov-21 5:00:30 PM

Copy test case

From the web portal, you can copy test cases from within a project or another project to a test suite, or you can use the Grid view to copy and paste test cases from one suite to another. Optionally, you can bulk import and export test cases.

Tip

Don't copy test cases when you want to test with different configurations or different data.

You have the flexibility to copy test cases from either within a project or from another project within the organization or collection. Additionally, you can choose to include all links and attachments during the copying process.

1. Select Test Plans > Test plans.

2. Choose the Test Plan that contains one or more test cases you want to copy from the Mine or All page.

3. Select the Test Suite that contains one or more test cases you want to copy.

4. From the Define page, select the check box for all test cases you want to copy.

5. Select More actions > Copy test case.

   

6. Choose the Project from the dropdown menu, and then enter the Test Plan Name or ID and Test Suite Name or ID. You can also select the name or ID from the dropdown menus.

   

7. (Optional) Select the check boxes for Include existing links and Include existing attachments.

8. Create the copy.

   The background copy operation depends on the quantity and complexity of the selected test cases. After completion, a notification gets sent to you confirming the operation’s success and a link to the test suite where the copied test cases reside.

Copy and paste test case (Grid view)

When you're managing test cases, copying and pasting serve as a valuable technique to reuse the same tests across various suites and plans. For instance, consider a scenario where you have a comprehensive test suite, and you want to create a more focused subset of tests within another suite. The Define > Grid view provides support for both editing test cases and copying them to different test suites. For more information, see Create test cases, Use the Grid view to edit test cases.

Tip

Don't copy test cases when you want to test with different configurations or different data.

From the Internet Explorer, Microsoft Edge, or Chrome browsers, you can copy test cases from the Grid view for one test plan and test suite to another test plan and test suite.

1. From the Test Plans > Test plans page, choose the test suite containing one or more test cases you want to copy. Within the Define tab, select Grid View.

2. Highlight the rows you want to copy, and then enter CTRL+C.

   

3. Select a different test suite from the same or different plan and paste with CTRL+V. If you don't select a different suite, nothing happens when you paste, because each suite can only have one reference to any test case.

4. Choose Save test cases.

   The new test cases save with new IDs assigned.

   

Bulk import or export test cases

From the web portal, you can perform a bulk import or export of test cases from/to a test suite. Test cases are defined in a comma-separated values (CSV) file.

Export test cases

1. From the Test Plans > Test plans page, choose the test plan with the test suite containing the test cases you want to export.

2. Optional. Choose Column options to add fields to include in the download file.

3. To export all test cases for the test suite, choose Export test cases to CSV.

   

   To export a subset of test cases for the test suite, select the test cases to export, choose More options, and select Export test case(s) to CSV.

   

4. The exported CSV file appears in your Downloads folder.

Import test cases

1. From Test Plans > Test plans, choose the test plan with the test suite into which you want to import test cases.

   

2. Choose the file to import from the opened dialog, and then select Import.

   

3. Select Confirm. If you specify test cases that are already defined in the test suite, some elements might get over written during import.

Import automated test cases (TCM)

To import automated test cases to a test suite, use tcm testcase /import. You must specify a .dll file for the test assembly that contains your tests.

tcm testcase /import /collection:teamprojectcollectionurl /teamproject:project
             /storage:path
             [/maxpriority:priority]
             [/minpriority:priority]
             [/category:filter]
             [/syncsuite:id [/include]]
             [/login:username,[password]]

Parameter	Description
/storage:path	Specifies the path and name of the test assembly that contains your automated tests that you want to import.
/maxpriority:priority	Optional. Specifies which tests to import based on the maximum priority of the test method. For example, if the parameter is /maxpriority:1, only tests with a priority attribute for the test method less than or equal to 1 are imported as test cases from the assembly.
/minpriority:priority	Optional. Specifies which tests to import based on the minimum priority of the test method. For example, if the parameter is /minpriority:2, only tests with a priority attribute for the test method equal or greater than 2 are imported as test cases from the assembly.
/category:filter	Optional. Specifies which tests to import based on the category of each test method in the test assembly. You can use this parameter together with /syncsuite to import tests with a certain category into a specific test suite. For more information about test categories, see Run unit tests with Test Explorer.
/syncsuite:id	Optional. Specifies the suite ID for the test suite in your test plan to which you want to add the test cases that you import. This suite can't be a dynamic suite or a query-based suite. If you specify a test suite to synchronize to update added tests, the tests that aren't imported are removed from the test suite but not from the test plan itself.

For descriptions of /collection, /teamproject and /login parameters, see Work with the TCM command-line tool.

Limitations

• The test case state column must be in Design state.
• The test case title length must not exceed 128 characters.
• There's a limit of 20 MB on JSON objects created during import and export. If the import fails, try the operation with small subset of the test cases.
• The user performing the import must have permissions on the area and iteration paths for test plan and test suite they're planning to import or export.
• Copy and Import operations fail if the related link count exceeds 1000 for the test case.

REST APIs

You can copy and clone test plans and test suites using the following REST APIs.

• Test Plan Clone - Clone Test Plan
• Test Suite Clone - Clone Test Suite

Next steps

Run manual tests

Related articles

• Create test plans and test suites
• Create test cases
• Share steps between test cases
• Test different configurations
• Repeat a test with different data
• Test objects and terms
• Create a query based on build and test integration fields
• Customize and manage the test experience