Question about Test Case migration (documentation)

[CBuntrock]

Hi all,

I just read the docs _howto/migrating-plans-and-suites.md on how to migrate the test cases with shared steps connected. From my understanding, the easiest approach would be to:

• Migrate all Non-Test items first (using ReflectedWorkItemID field)
• Migrate Test Cases and Shared steps/params together (using IntegrationBuild field)
• Migrate the other meta data of testing items (suites, plans etc.)

I think this is also how the docs recommend it. My question would be this: Since test cases are not included in Step 1, why do we need the field mapping to populate IntegrationBuild field? Since we anyways do not yet copy test cases or shared steps, I would assume we do not need this field mapping...

Thanks!
Best,
Chris

[MrHinsh]

When you migrate the Test Cases it needs to be able to find linked work items. Since you are migrating them using IntegrationBuild, but the other items used ReflectedWorkItemID it would not be able to find them. This ensure that all work items in scope for your migration are discovered correctly.

[CBuntrock]

Thanks for the response!
Assuming someone wants to migrate Non-Test and Test items in separate operations, wouldn't it work to do it this way...?

• Migrate all Non-Test items first (using ReflectedWorkItemID field)
• Migrate Test Cases only using ReflectedWorkItemID + add FieldMap (similar to step 1 in the docs) to IntegrationBuild field
• Migrate Shared steps/params using IntegrationBuild field (similar to step 2 in the docs)
• Migrate the other meta data

This way someone could first migrate non-test items using default reflectedworkitemID field and then migrate test items afterwards. The separate run of test cases upfront before shared steps makes sure all test case related ID values are in both fields.

Best,
Chris

[MrHinsh]

Yes, that sounds like it would work.