Determining Which Builds Have Bug Fixes, New Features, or Requirements
Using Microsoft Test Manager you can determine the changes between two builds, if the application that you are testing is built by using Team Foundation Build. This lets you determine whether you should begin to use a different build of the application for your testing, based on what has changed. For example, if you know that a new build has a bug fix for an issue that is blocking many of your tests, you might decide to assign the build to use with your test plan.
You can also see whether a requirement or a user story has been implemented in a new build. If a requirement has been implemented, you might want to set the test suite for that requirement to be in progress.
To select from the build candidates that you want to consider using for your test plan, you have to select a build filter for your test plan. After you have selected the build you are currently using to test, you can select a later build to see which work items have been associated with each of the builds between these two selected builds, as shown in the following illustration.
.png "Select Build")
Note
To be displayed in this associated work items list, work items must be associated with the changeset when a user checks in code changes.
Tasks
Use the following topics to help you determine which builds have bug fixes, new features or requirements:
Tasks |
Associated Topics |
|---|---|
Selecting a build filter and build for your test plan: You might want to set up a build filter for your test plan to limit the build candidates that are displayed. Then you can select the build you are currently using to test. |
|
Associating Completed Work With a Changeset: When coding changes are checked in, you must make sure that they are associated with a work item that they resolve. To associate a work item with a changeset, you must create an associate link type with the work item when you check in a changeset to version control. For example, if the code changes complete the implementation of a requirement then the check-in for the changes must link to the requirement. |
|
Determining Which Builds Have Bug Fixes, New Features, or Requirements You Want to Test: You must select the build for your test plan that you are currently using to test. You can then view which work items have been associated with any builds that occurred after your current build for your test plan. |
How to: Determine Changes Between Builds and Use a New Build for Testing |
Setting Test Suites To Be Ready To Test: If a requirement or a user story has been implemented in a specific build, you might want to set the test suite for that requirement to be in progress. |