Do you create one test plan per Sprint?

Last updated by Brady Stroud [SSW] about 1 month ago.See history

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

You could create 1 test plan that you use for all milestones and add test suites and tests as you progress. This is not a good approach because you then do not have historical data for your test pass rates for previous milestones.

project test plan bad
Figure: Bad Example – no historical data for your test pass rates for previous milestones

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 to help you understand whether the quality of your application is improving.

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

Tip: If you add both manual (scripted or exploratory) and automated tests to your test suites, you can view the overall testing status based on both of these types of tests for your test suites and test plans.

Reference: Create test plans and suites

We open source. Powered by GitHub