Secret ingredients to quality software


Do you create one Test Plan per Sprint?

Created on 19 Aug 2013 | Last updated by Tiago Araujo on 19 Aug 2013 07:47 PM (over 7 years ago)

When you use Microsoft Test Manager to create test plans and test suites for your team project, there are several approaches that you can take.

project test plan bad
Figure: Bad Example – Only create 1 test plan that you use for all milestones. Add test suites and tests as you progress. This is bad because f you use this approach, you do not have historical data for your test pass rates for previous milestones

project test plan good
Figure: Good Example - Create test plans based on your testing goals for a specific sprint

By creating test plans for each sprint, you can see when a sprint is complete, based on your testing goals. You can also prepare the test plan for the next sprint while you complete your testing for the current sprint. By using this approach, you can track your testing progress for each of your test plans and see that the quality of your application is improving.

Tip: If you add both manual and automated tests to your test suites, you can view the overall quality based on both of these types of tests for your test suites and test plans.

Reference: Guidance for Creating Test Plans and Test Suites

Adam StephensenAdam Stephensen

We open source. This page is on GitHub