170 Part II: Team System for the Entire Team
Figure 7-16 The Ordered Test Designer being used to create a QA test run
Tip Ordered tests can contain other ordered tests. You can use this to your advantage by
constructing smaller, more focused ordered tests and then chaining them together in a
specifi c order to test broader functionality.
Test Results and Tracking Bugs
Executing any kind of test generates some results that testers will use to determine whether
a defect exists or if a Quality of Service requirement wasn’t met. These situations will require
action. All test results for recently run tests are available through the Test Results window.
Figure 7-17 shows the Test Results window with results from running a variety of the tests
mentioned in the last section. You can quickly identify which tests have run, are in progress,
and are awaiting execution. You can also easily identify which tests have passed and those
that have failed.
Figure 7-17 The Test Results window displaying execution status and results for all test types
Double-clicking a test displays either the results for that test if it has completed or the
appropriate runner if the test is in progress. From a failed test, a tester can easily create a
bug work item and assign it to a developer. The developer can query for this work item or, if
properly confi gured, he or she will receive a notifi cation (such as an e-mail) indicating that
a new work item has been assigned. The developer can then easily retrieve the recorded test
Chapter 7: Testers 171
results. After the developer fi xes the bug and marks the work item as completed, he or she
could generate a new task work item asking the tester to rerun the test.
Bug work items can also be tracked by managers through the many queries and reports
provided on the project portal Web site. Achieving this level of collaboration is what Visual
Studio 2005 Team System is all about. This type of communication and workfl ow can really
help maintain or increase the predictability of a project’s success.
Microsoft will include many reports related specifi cally to testing:
Test run results in general
Tests that passed (but that have associated bugs that are still showing as active)
Tests that failed (but that have associated bugs that are currently closed)
Test effectiveness (showing a combined list of test results and the resulting code
coverage numbers)
Test Run Confi guration
Test run confi gurations affect how your tests run. When you defi ne a test run confi guration,
you determine, for example, the way test runs are named, where the tests are executed,
and whether unit tests generate code-coverage information. Figure 7-18 shows a Test Run
Confi guration fi le being edited and a remote server being specifi ed as the location where the
tests will be run remotely.
Figure 7-18 A Test Run Confi guration fi le being edited
Run confi guration settings are saved to disk in fi les with the .testrunconfi g extension.
You can create and save multiple run confi gurations, and then make a specifi c run
confi guration active, which is the run confi guration that is used when tests are run. Only
one run confi guration can be active at a time. Your choice of an active run confi guration is
maintained from one user session to the next.

Get Working with Microsoft® Visual Studio® 2005 Team System now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.