System Testing Your Application Using Microsoft Test Manager
Using Microsoft Test Manager you can plan, manage, and execute both manual and exploratory tests. You can also automate your manual tests once they are stabilized. While you are performing manual and exploratory tests, you can log bugs. The bug will contain a trace of your recent actions, a snapshot of the state of the system, and a copy of any notes you made while exploring the system. You can record your actions in the test case, so that they can be played back later.
You can also use Microsoft Test Manager to set up and manage lab machines. You can configure a virtual lab in which to install a distributed system, and link that lab to the test plan. Whenever you need to repeat tests—for example when you want to publish a change to your system—the lab can be reconfigured automatically.
Videos
Easily reproducing issues through manual testing
Managing lab environments for testing
Related Tasks
Task |
Related topics |
---|---|
Get familiar with Microsoft Test Manager: Use these links to learn how your team can use Microsoft Test Manager as part of your application lifecycle. |
|
Planning your testing effort: Plan your testing based on either requirements or user stories. You can link your tests to these requirements or user stories and then plan which configurations you want to use to run these tests. Alternatively, you can create test suites using other criteria to plan your testing effort. |
|
Creating and managing tests: Create and manage both manual and automated tests as part of your plan. You can create test cases to be run as manual tests with individual test steps from Microsoft Test Manager. Automated tests, such as unit tests, load tests and automated UI tests, can be created by using Visual Studio. Later, if you want, you can convert test cases to automated tests by linking automation to the test case. |
|
Running your tests: Run your manual, exploratory and automated tests from a test plan using Microsoft Test Manager, save these test results, and use to measure your testing progress. |
|
Tracking software quality: Measure your testing readiness, track your testing progress, and view the status of bugs. The bugs include detailed information that is collected when you run your tests using Test Runner. You can also submit bugs from Microsoft Test Manager. |
|
Review and track test results: After you run tests, review your test results to see which tests passed and which tests failed. You can then assign a reason for a failed test, and assign a resolution. You can view all the test results for a test plan using pre-defined test reports or by creating your own custom reports. If your team uses a project portal, you can view the pre-defined reports on the Test Dashboard. Access the project portal from the Track view in the Testing Center in Microsoft Test Manager. For more information about the project portal information, see Test Dashboard (Agile). |
External resources
Guidance and hands-on labs
Testing for Continuous Delivery with Visual Studio 2012
CodePlex – Test Infrastructure Guidance
Visual Studio Test Tooling Guidance
Visual Studio Lab Management Guide
Videos
Easily reproducing issues through manual testing
Managing lab environments for testing
Forum
Visual Studio ALM + Team Foundation Server Blog