Before you can run any tests you first need to have a Test Plan.  As discussed in an earlier section, we will be creating Test Plans for each phase of testing: Implementation Testing and Release Testing.

For the Implementation Testing Phase, each team will create a Test Plan for each of their Sprints. For example, if there are 20 teams each on 2-week sprints, that results in approximately 40 new Test Plans each month.

Each Implementation Test Plan should contain a Test Suite for each User Story that is part of that Sprint.  Those Test Suites will in turn contain the Test Cases for each User Story.

Creating a Test PlanEdit

At the start of each Sprint create a Test Plan by following these steps:

  1. Open MTM
  2. Click the Home button
  3. Click Add to create a new Test Plan
  4. Enter the plan name in the format Team 07 - Sprint 03
  5. Select the appropriate Area and Iteration that corresponds to your team and current Sprint
  6. Click Add
  7. Select your newly created Test Plan in the list and click Select Plan
  8. Go to Test Plan Properties
  9. Under Test Settings select CoreLink
  10. Click Save and Close
  11. Click Add Requirements, this will allow us to quickly create a Test Suite corresponding to each User Story in this Sprint
  12. Customize the default Query so it filters to only items under our Teams Area Path and only items under the relevant Iteration Path (see screenshot below)
  13. Click Run
  14. This should list all User Stories in the current Sprint.  Select them all and click Add Requirements to Plan
  15. We should now have a Test Suite for each User Story in this Sprint.  Within each Test Suite we now need to add Test Cases.  We can either click New to create a new Test Case, or click Add to add a pre-existing Test Case (reuse).

Retiring a Test PlanEdit

When a Sprint is completed we should retire the Test Plan so it doesn't continue to clutter up the list of active Test Plans:

  1. Go to Test Plan Properties (on the Plan tab)
  2. Change the State to Inactive
  3. Save the Test Plan

See Also: How to Write High Quality Test Cases