Replies: 1 comment
-
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.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Migrating Plans and Suits is quite convoluted since Shared Steps, which we need to map, can't have a custom field.
Test Cases
with theirShared Steps
andShared Parameter
Test Variables
&Test Configurations
Test Plans
&Test Suits
WARNING: The configs below are for illustration and were correct as of the version number in the
Version
field.1. Migrate Basic Work Items
This will migrate all of the work items, while also populating
IntegrationBuild
. Ensure that you have a Field Map that will copyReflectedWorkItemId
toMicrosoft.VSTS.Build.IntegrationBuild
.The important bits:
ReflectedWorkItemId
toMicrosoft.VSTS.Build.IntegrationBuild
2. Migrate
Test Cases
with theirShared Steps
andShared Parameter
This will migrate Test Cases while fixing the links to the Shared bits that can't be customised. This will use the
Microsoft.VSTS.Build.IntegrationBuild
to wire everything up as needed. It will also copy theMicrosoft.VSTS.Build.IntegrationBuild
toReflectedWorkItemId
for Test Cases so that we can also use them with work items.The important bits:
Microsoft.VSTS.Build.IntegrationBuild
toReflectedWorkItemId
for Test Cases only3. Migrate
Test Variables
&Test Configurations
These are pre-requisites for rebuilding the Plans and Suits.
The important bits:
Test Variables
&Test Configurations
4. Rebuild
Test Plans
&Test Suits
This will rebuild the Plans and Suits and wire up all of the Test Cases.
note: Runs are not migrated.
The important bits:
TestPlansAndSuitesMigrationConfig
Beta Was this translation helpful? Give feedback.
All reactions