Exercise 3: Selecting Builds to Test Against
In this exercise, you will learn how to use the Track activity to navigate and select the builds to test against.
- In Microsoft Test Manager, select the Track tab to open the track activity. By default, the Queries window is loaded.
Select the Assign Build link to view the available builds and associated work items.
Figure 1
Assigning builds for testing
In the Available Builds drop down, select the last build in the list (Tailspin Toys – Iteration 2_20100318.4).
Figure 2
Selecting a build
Look at the associated work items to see what work was done during the selected build. Note that a single work item to “Write regular expression for strong password” was completed.
Figure 3
Associated work items
- Select the Tailspin Toys – Iteration 2_20100318.5 build from the Available Builds drop down. There are three associated work items for this build, one of which is the same work item as before.
The Track activity can be used to help determine when it will be worthwhile to perform a test pass.
Select the Toys – Iteration 2_20100318.6 build from the Available Builds drop down and select the Assign To Plan button. This will help provide an indication to the testers that this build warrants doing a full test run. Future test runs will use the new build by default.
Figure 4
Assigning a new build to the test plan
When notified that some tests may need to be run again based on code changes, choose to view the recommended tests.
Figure 5
Option to view recommended tests
- These recommendations are made possible by a new feature called Test Impact Analysis, which is able to determine when code changes impact previously executed tests. For example, a test that was successfully executed against an earlier build may be recommended to be executed again if it is determined that (a), code has changed and (b), that it is in the code path exercised by that test.
Test Impact Analysis can be configured to run in the background when the application being tested is written in managed code (.NET Framework 2.0 or higher).
Select all recommended tests that are impacted by this latest build and select the Reset To Active button. This resets the state of test cases within the test plan to the Active state.
Figure 6
Resetting test case state to active for recommended tests
Return to the Test activity window and select the Run Tests link.
Figure 7
Return to Test activity
Select test suite 7. Note that the two test cases there were previously in the Passing state are now Active again.
Figure 8
Test cases were reset to Active state
Return to the Track activity window, select the Recommended Tests link, and select the Related Work Items button. Note that a number of work items that have been closed or resolved since build Tailspin Toys – Iteration 2_20100318.3, including a user story work item.
Figure 9
Related Work Items
- Return to the Test activity window and select test suite 8, which is associated with the impacted user story that we just looked at in the previous step.
Select the blocked test cases and then select the Reset button to unblock them. Their state goes from Blocked to Active.
Figure 10
Location of Reset button
Select the Verify Bugs link. Although we will not do so in this lab, this is where testers could select previously reported bugs and re-run the tests. If the tests do not pass, the testers would re-assign the bugs back to the developers.
To give feedback please write to VSKitFdbk@Microsoft.com
Copyright © 2010 by Microsoft Corporation. All rights reserved.