How-to: Migrating Plans and Suites #2049
Replies: 8 comments 20 replies
-
Great article! First I thought that step 2 would only migrate test cases, but in the logs it looks like it goes through all work items again. |
Beta Was this translation helpful? Give feedback.
-
Hello MrHinsh, |
Beta Was this translation helpful? Give feedback.
-
I am migrating my test plans suites and variables while migrating the test plans (suppose I have 1 test plan but I do not want 2 test plans )using below query it is taking all test plans but do not want two test plans which i mentioned in below query "WIQLQueryBit": "AND [System.WorkItemType] = 'TestPlan' AND [System.Title] NOT IN ('plan name 1', 'Plan name 2')" How can i Update the query please let me know. |
Beta Was this translation helpful? Give feedback.
-
@MrHinsh Please help and give me the correct query or a sample file how to exclude test plans |
Beta Was this translation helpful? Give feedback.
-
Question - Do we have to run these steps one by one or all of these setps can be configured in order? I intend to test the scenario anyways but it would be good to know : TIA |
Beta Was this translation helpful? Give feedback.
-
@MrHinsh After test plans, suites migration can we execute the test case using naked agility version 16.0.9 or do we need to execute manually |
Beta Was this translation helpful? Give feedback.
-
@MrHinsh I am facing an error like sequence contains more than one element while migrating test plans below are the examples. suppose I have one test plan name with DEV and inside DEV we have two test suites DEV1 and DEV2 error -- 2025-04-04T04:44:48.3934243Z [04:44:47 FTL] [16.0.9] Error while running TfsTestPlansAndSuitesMigrationProcessor Please help. |
Beta Was this translation helpful? Give feedback.
-
I assume if you only want to migrate Test Plans/Suites/Cases, you can skip step 1 "Migrating Basic work items". Correct? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Migrating Plans and Suits is quite convoluted since Shared Steps, which we need to map, can’t have a custom field.
WARNING: The configs below are for illustration and were correct as of the version number in the Version field.
https://nkdagility.com/learn/azure-devops-migration-tools/howto/migrating-plans-and-suites/
Funding for us doing work on this tool is generally through 1) customer funding, or 2) donated free time.
Sponcer a Feature | Hire us directly
Beta Was this translation helpful? Give feedback.
All reactions