The test runtime engine produces test results of various kinds, depending on the types of tests you have run. All test types share the following behavior:
For all test types, the test name and a test result are displayed as soon as the test run starts. The result, such as, Pending, In Progress, Inconclusive, Pass, and Fail, is updated in real time throughout the test run. For certain test types, Web and load tests in particular, more extensive data is reported as the test is running; see Results of Specific Test Types.
Note |
|---|
| You can change the display of the Test Results window in various ways, such as filtering to show only specific test runs. For more information, see How to: Adjust Test Results Views. |
You can pause, stop, and resume a test run using buttons on the Test Results window. As you do this, the test result is updated to reflect the current state of the test run. For more information, see How to: Pause, Resume, and Stop a Test Run.
When the test run is completed, its results are written to disk. For more information about identifying and using the file in which they are stored, see How to: Import Test Results.
Note |
|---|
| Running tests remotely is an asynchronous operation. You can start a remote test run, close Visual Studio, and the tests will continue to run. After you restart Visual Studio and connect to the remote run, the test results are displayed in the Test Results window. |
Test Results Details Page
For all test types except Web and load, the test Results Details page displays all the information shown in the Test Results window, plus additional in-depth test results about an individual test. To do this, in the Test Results window, click the test result and press Enter, double-click the test result, or right-click the test result and then select View Test Results Details.
Note |
|---|
| Detailed test results for specific, individual test types, are displayed in this window. This page will be especially useful to those who customize Team Edition for Testers and who want to add new types of viewers for specific test results. |
This window also displays certain errors that can cause a test to fail, such as the following:
-
A container test, specifically a load test or an ordered test, is empty and therefore could not be run.
-
One or more per-test deployment items could not be found and deployed.
Test Run Details Page
After you run tests, the overall status of the test run is displayed in the status bar of the Test Results window. This status is for the entire test run, not for the individual tests that it contains.
To see in-depth results for the entire test run, open the Test Run Details Page. To do this, click the status link on the status bar. The wording of the status link reflects the status of the test run: Test Run Error, Test Run Inconclusive, Test Run Failed, or Test Run Completed.
The Test Run Details Page displays general information about the test run, including the test run configuration that was active when it was run. It also states how many of the tests in the run passed, failed, or were skipped, and it describes any errors that were encountered, such as failure to instrument binary files.
This window also displays certain errors that can cause a test run to fail, such as the following:
-
Deployment files specified in the run configuration could not be deployed.
-
Code coverage failed because assemblies could not be instrumented.
-
Code coverage failed because information could not be gathered.
-
After a remote test run, files could not be copied from the controller.