Tuesday, March 1, 2011

Microsoft Test Manager Test Case Versioning

***Updated Nov 5, 2011 - I have created a tool to help with the bulk copying of Test Cases and updates the Iteration field at the same time Bulk Copy Test Cases Tool

I was recently asked at my training classes how do I manage Test Cases over multiple releases using Microsoft Test Manager.
Copying the test cases and changing the iteration path is what you can currently do today.  In addition, managing your testing efforts is really controlled by what you put in your test plan/test suites.
  • Test Case A is created for product release 1.0.
    • Create the test case and set the iteration to 1.0
  • Test Case A is slightly modified for product release 1.1 (small changes to the feature).
    • Copy test case and change the iteration to 1.1
  • Test Case A is more significantly modified for product release 2.0 
    • Copy test case and change the iteration to 2.0
  • Now I need to make a 1.0.1 release (1.0 patch).  I want to run the 1.0 version of Test Case A (rather than maintaining entirely separate copies of my test cases per release).
    • Create a query-based suite in your test plan named “1.0 patch”.
    • Create a query that returns Test Case A and is equal to iteration 1.0
  • What’s the best practice for managing multiple copies of test cases in this scenario?
    • When you create multiple copies of a test cases it automatically creates a related link. If you want to see the links on an individual work item basis you can see it under the Other Links tab. If you want to see more work items, you can create a Work Items and Direct Link query that will query test cases that return the selected related link type.
Hope this helps,

Anna Russo
Sr. ALM TFS Software Process Consultant


  1. Thanks Anna, it's open my mind for many helpful ideas, keep up the good work!

  2. Thanks Anna, I have been searching for something that would help me establish a process for test case management in MTM. The solution you have provided is not the best solution that I would like but it at least gives a workaround to tackle this problem.

  3. Yes the approach described here will remain. I will be publishing 2012 post shortly.