[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]
If you have Visual Studio Test Elements 2010 or Visual Studio 2010 Ultimate, you can run manual tests and automated tests from a test plan using Microsoft Test and Lab Manager. When you run any of these tests from your test plan, you can save your test results into the team project for your Team Foundation Server. You can now view the progress of both your automated and manual tests together from your test plan.
If you have Visual Studio 2010 Ultimate or Visual Studio 2010 Premium, you can run automated tests from Microsoft Visual Studio 2010 or from the command line. You can also run tests using Team Foundation Build. Test results are created every time that you run a group of tests.
To run manual tests, you must use Microsoft Test and Lab Manager to run your tests from a test plan as shown in the following illustration. Then you can view your test results from your test plan.
.png)
After you have created any of the following types of automated tests using Microsoft Visual Studio 2010, you can use Microsoft Test and Lab Manager or Microsoft Visual Studio 2010 to run the tests.
Unit tests
Database unit tests
Coded UI tests
Load tests
Generic tests
For example, if you want to run your automated tests and see the results immediately, you can just run your tests from Microsoft Visual Studio 2010 and view the test results as shown in the following illustration.
.png)
If you want to run your automated tests and have the results added to a test plan, you can associate your automated tests with test cases using Microsoft Visual Studio 2010, create test settings and an environment for your test plan for automated tests, and then run them using Microsoft Test and Lab Manager as shown in the following illustration.
.png)
Use the following topics to help you run your tests:
Tasks | Associated Topics |
|---|
Setting Up How to Run Your Tests: You can define where to run your tests and what data to collect or how to affect the test machine when you run your tests using test settings. If you have a multi-tier application, you can select a set of roles for this. You can then use a physical or virtual environment that contains these roles to run your tests from your test plan. Or you can use a test agent controller and test agents when you run your tests by using Microsoft Visual Studio 2010. | |
Running Manual Tests from a Test Plan: You can run manual tests from your test plan using Test Runner to record if each step passes or fails. The test outcome and any data that is collected when you run the test can be saved. You can also submit bugs when you run your manual tests. | |
Speeding Up Manual Testing: You can record the UI actions that you take when you run a manual test. When you run the test again, you can play back the action recording that you created to automatically perform these actions. | |
Running Automated Tests: You can run tests directly from Microsoft Visual Studio 2010, from Microsoft Test and Lab Manager, from Team Foundation Build, or from the command line. You can use mstest.exe to run your automated tests from the command line, or you can use tcm.exe to import your test methods into test cases. You can then run the test cases for specific configurations from the command line and save the results for the appropriate test plan. You can also submit bugs for any issues that you find. | |
Finding Tests That Need to Be Run: You can find which tests are recommended to run based on code changes to the application under test. You can also check which builds have specific bugs that have been fixed or new features or requirements, and then determine which tests to run. | |
Analyzing Test Results: You can analyze the test results for your automated tests for each test run. You can also review the code coverage results to check that your tests are really testing as much of your application as possible. | |
Customizing How Your Tests Are Run: You can create your own diagnostic data adapters to collect specific data or impact the system when you run your tests. | |
Concepts