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:
- Open MTM
- Click the Home button
- Click Add to create a new Test Plan
- Enter the plan name in the format Team 07 - Sprint 03
- Select the appropriate Area and Iteration that corresponds to your team and current Sprint
- Click Add
- Select your newly created Test Plan in the list and click Select Plan
- Go to Test Plan Properties
- Under Test Settings select CoreLink
- Click Save and Close
- Click Add Requirements, this will allow us to quickly create a Test Suite corresponding to each User Story in this Sprint
- 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)
- Click Run
- This should list all User Stories in the current Sprint. Select them all and click Add Requirements to Plan
- 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:
- Go to Test Plan Properties (on the Plan tab)
- Change the State to Inactive
- Save the Test Plan
See Also: How to Write High Quality Test Cases