Quick Start Guide for Manual Testing using Microsoft Test Manager
This is a Quick Start Guide for manual testing using Visual Studio Ultimate or Visual Studio Test Professional The guide helps you get started quickly by describing how to create manual tests, run them and record the results by using Microsoft Test Manager.
The following procedures describe the key steps for this Quick Start Guide:
First, you must connect to the appropriate team project. Select the team project that is used to develop the application under test and store your requirements or user stories. This is where your testing artifacts will be stored.
Only team projects that you have permission to access will be displayed. For more information, see Team Foundation Server Permissions.
To connect to your team project and create a plan
Open Microsoft Test Manager.
To display the Microsoft Test Manager window, click Start, and then click All Programs. Point to Microsoft Visual Studio 2010 and then click Microsoft Test Manager 2010.
To add a new Team Foundation Server for the first time, type the URL, or just the name of the Team Foundation Server, and then click Add.
The connection string that will be used to connect to Team Foundation Server is shown in Preview.
If you do not know the name of your Team Foundation Server, contact your system administrator.
To select a team project collection, click the arrow to view the list of team projects for this team project collection.
For more information about team project collections and team projects, see Organizing Your Server with Team Project Collections.
Select the name of your team project in the list, and then click Connect.
If you successfully connect to this team project, the Testing Center is displayed.
You can select an existing test plan to use or add a new one. To select an existing test plan to use, click the plan in the list and then click Select Plan.
To add a plan, click Add.
The Add test plan dialog box is displayed.
Type the name for your plan in Enter the plan name, and then click Add.
Your plan is now added to the list and highlighted.
(Optional) To create a URL that other team members can use to connect to this plan, click Copy URL for plan.
This copies the URL to the plan you created to the clipboard. You can now paste this URL into an email and send it to others in your team so that they can easily connect to the plan. For more information, see How to: Switch between Test Plans Using URLs.
To select the plan you added, click Select plan.
The Contents view for your test plan is displayed. Now follow the steps in the next procedure to add the details of your test plan.
Before you create test cases and run them, you must have a test plan. The details that you can add to your test plan are shown in the following illustration. You can update the test plan at any time. The following procedure describes the minimum changes that you might want to make to your test plan properties.
To add details to your test plan
To change to the properties view for your test plan, click Properties.
(Optional) To change to a different iteration for your team project, click Iteration.
(Optional) The default configuration provided for the test plan specifies that the tests should be run on the Windows 7 operating system using Internet Explorer 8.0 as the browser. You can just use this as a placeholder to get started, or you can create a different configuration with different default values, or different configuration variables. To add new configurations, click In this plan under Configurations, and then click Manage. For more information, see Defining Your Test Matrix Using Test Configurations.
Configurations are part of planning and inform the tester what is required. When the tests are run, there is no verification that the tests are actually running on that configuration.
To save any changes, click Save and Close.
You can update your test plan at any point. For more information that is not covered in this Quick Start Guide about what you can do with your test plan, see How to: Create a Test Plan.
The Contents view is displayed. You can now follow the steps in the next procedure to create your manual test cases.
You can just add test cases to the default test suite that has the same name as the test plan, as shown in the following illustration.
Or you can add requirements to the test plan and add your test cases to these requirements.
When you create manual test cases, you can add the action and expected result for each test step, as shown in the following illustration. When you run this test, you will be able to mark each test step as either passed or failed.
To create manual test cases
To show the contents of the test plan, click Contents.
(Optional) To create a new test suite by using a requirement, click Add requirements.
The Add existing requirements to this test plan dialog box is displayed.
(Optional) Select any requirements that you want to add to the test plan, and then click Add requirements to plan.
For this Quick Start Guide the test suites that were created from the requirements are added to the default suite that is the root node with the same name as the test plan. You can add test cases or test suites to this test suite root node, but you cannot rename it. For more information about how to organize your test cases with test suites, see Organizing Test Cases Using Test Suites.
To add test cases to the default test suite or a suite created from the requirements, select the test suite in the test suite hierarchy pane and then click New in the test suite details pane.
The New Test Case dialog box is displayed.
Enter the details for your new test case including the title, actions, and expected results for each test step, and then click Save and Close.
The new test case is now displayed in the test suite details pane.
If the test case is created for a test suite based on a requirement, the test case will automatically be linked to the requirement.
You can now run the tests in your test plan. Each pairing of the default configurations and test cases in the test plan is displayed in the Test view. You can select the tests that you want to run, as shown in the following illustration.
Then you can start the test from Test Runner.
You will be prompted to start a test and you will have the option to create an action recording. An action recording can be used to play back the actions that you perform when you run your test. For more information about action recordings, see Recording and Playing Back Manual Tests.
Start the application under test and perform the test steps. As the test runs, mark steps as either passed or failed; add comments, files or screen shots; or create a bug, as shown in the following illustration.
To run manual tests
In the center group menu bar, click Test.
To run the tests, select the test suite that contains the tests that you want to run.
The pairings of the tests and configurations are shown in the list.
Select the tests you want to run and then click Run.
Test Runner opens.
In Test Runner, you are prompted to Start test and optionally you can select Create an action recording. Click Start test.
You can increase the speed and efficiency of tests using action recordings. For more information about how to create an action recording, see How to: Create an Action Recording.
Perform the steps in the test case.
Any data associated with a test step is displayed with the step.
To mark the result of a test step, click the drop-down for the active icon to the right of the test step and then click either Pass or Fail.
To pause the test at any time, click Pause. If you are recording the test case, clicking Pause also pauses an action or video recording. To resume the test and the action or video recording, click Resume.
If you find a bug, click Create bug.
The New Bug dialog box is displayed. Any data that you have attached or collected will automatically be added to the bug. For more information, see How to: Submit a Bug using Test Runner.
When you have finished testing, click End test.
A result for the test is now shown in Test Runner, based on the test step results. If you chose to record the test, the recording is automatically stopped and saved.
The overall result for a test is based on the status for all the test steps that were marked. Therefore, if one test step is marked as failed then the test will have a status of failed.
You must mark a test step with a status if it is a validation test step. Otherwise, the test will be automatically marked as failed.
To save your test results, click Save and Close.
You can now track your progress for your test plan. After you run your manual tests with Test Runner, you can immediately view your progress in the Run Tests activity. You can view the tests that have passed and failed. You can mark tests as blocked or reset tests to active when you are ready to run them again, as shown in the following illustration.
To track testing progress
The progress bar is a graphic representation of your testing status, based on the percentage of tests in a particular state. Tests in a similar state are shown with the same color, so that you can quickly view your status. The states are defined in the following table.
Tests that have passed.
Tests that have failed.
Tests that are blocked
Tests that need to be run. This includes tests that have not been run at all, blocked tests that have been unblocked and failed tests that have to be rerun because an issue has been fixed.
Any tests that are currently running
To view a summary of your testing progress, move your mouse pointer over the progress bar in the Run Tests activity.
The dialog box that shows a summary of the status of all your tests is displayed.
To view the results for a specific test, select the test and then click View results.
The most recent test results are shown for that test together with all the details and any data that was collected when the test was run.
You can also view the Test Results History of each time the test has been run for this test plan in these test results. For more information about how to view test results, see How to: View Test Results Using Microsoft Test Manager.