How to: Run Multiple Manual Tests in a Test Suite
Running manual tests in a test suite using Test Runner can help you identify problems in software code. Problems that are typically identified when you run manual tests include incorrect functionality or bugs, poor performance, and security and connectivity issues. The outcome, resolutions, and comments that you can enter during a manual test are saved as test results.
This procedure describes how to run multiple manual tests that are contained in a test suite. Before you run a manual test, you must first create a manual test and add it to a test suite. For more information, see How to: Create a Manual Test Case and Organizing Test Cases Using Test Suites.
.png "Selecting test to run in Microsoft Test Manager")
For more information about keyboard shortcuts to use when you run a manual test, see Keyboard Shortcuts for Microsoft Test Manager.
To run a test suite
Open Microsoft Test Manager.
Note
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.
On the center group switcher, click the down-arrow and then click Testing Center.
On the center group menu bar, click Test.
In the menu under the center group menu bar, click Run Tests, if it is not already selected.
In the left pane, under Run Tests, select the test suite that is listed under the test plan that you want to test.
Note
You can click Filter to help you search for test matching. You can use the Tester drop-down list box to filter by the team member to whom tests are assigned, or you can filter by Configurations.
The right side pane displays the test cases in the selected test suite.
Note
When you run the tests from the test suite, the tests will be listed in Test Runner in the order that is shown in your test suite. You can change the order of the test in Microsoft Test Manager. For more information, see How to: Change the Order of Test Cases in a Test Suite.
Select one or more test cases and then click Run.
To select nonadjacent cases, click one case and then hold down CTRL and then click each additional case.
To select adjacent cases, click the first case in the sequence and then hold down SHIFT and then click the last case.
Note
Select Run with options to specify a build on which to run the test, or to override the test settings and environment settings for the test plan. For more information, see How to: Override Settings in Your Test Plan For Test Runs.
Test Runner opens.
Note
If this is the first time that you have tried to run a test after you installed Microsoft Test Manager, and you have not restarted your machine after you completed the installation, you will be prompted to restart your machine and start your test again.
In Test Runner, you are prompted to Start Test with the option to Create action recording. Leave the Create action recording check box cleared and click Start Test.
You can increase the speed and efficiency of tests by using action recordings. For more information about how to use the Create action recording option to create an action recording, see How to: Create an Action Recording.
Perform the steps in the first test.
Note
If any one of the steps in your test uses parameters, you will see this information displayed in the test steps. You can copy this data and use it in your application under test. For more information, see How to: Run Multiple Iterations of a Test Using Different Data Parameters.
During each step of the test, you have the option to perform the following tasks that are provided by the toolbar in Test Runner.
Task
Details
End the manual test.
To end the test at any time, click End test.
Pause and resume the manual test.
To suspend the test at any time, click Pause. If you are recording the test, clicking Pause also pauses the video recording or any other diagnostic data adapters. To resume the test, video recording and any other diagnostic data adapters, click Resume.
Reset the manual test.
During a test, you can reset the test by using Reset and then start the test again. For more information, see How to: Reset a Manual Test.
Submit a bug.
If you discover a defect in the application during a test step, you can submit a bug by using Create bug. For more information, see How to: Submit a Bug using Test Runner.
Submit an exploratory bug.
When you run an exploratory test and find a bug in the application, you can submit an exploratory bug by using Create exploratory bug. Submitting an exploratory bug in this manner lets you specify the time range for the actions to include in the bug. For more information, see How to: Submit an Exploratory Bug using Test Runner.
Capture a screen shot.
To help clarify issues that are discovered during a test, you can include screen shots when you test an application by using Capture rectangular screen shot. For more information, see How to: Capture a Screenshot While Running a Test.
Add a comment.
For each step in the test, you can include comments that provide details and useful information that you discover by using Add comment to step result. For more information, see How to: Add a Comment While Running a Test.
Attach a relevant file.
During a test, you can attach a file that is associated with the applications that you test, for example, an output file that the application generated. To attach a file to the test, use Add attachment to step result. For more information, see How to: Attach a File While Running a Test.
Take an environmental snapshot.
You can use Take environment snapshot to optionally attach a snapshot of the environment settings when you perform a test. For more information, see How to: Run Manual Tests and Create Reproducible Bugs With Virtual Environments.
To mark the result of a test step, click the drop-down exclamation mark to the right of the test step and then click either Pass or Fail.
Tip
You can select multiple steps and mark them as either passed or failed. Additionally, you can mark the entire test as either passed or failed.
You can use the global shortcut keys to mark a test step as follows without changing the input focus from the application under test:
Pass test step: Win+Ctrl+Q
Fail test step: Win+Ctrl+W
Note
If it is a validation test step and you do not mark the test step as passed or failed, the test result is automatically marked as failed. You should verify the expected results for all validation test steps and mark the test step based on the actual results.
When you have finished the test, click End test and move to next.
The Start Test dialog box is displayed.
(Optional) At the top of Test Runner, click the down-arrow next to Test <x> of <n>. All the selected test cases are listed and the current test case is highlighted. You can select the test that you want to run next.
.png "Run Multiple Iterations of a Test")
Repeat steps 7 through 11 until you have completed all the test cases.
In the toolbar at the top of Test Runner, click Save and Close to save your test results to the Team Foundation Server and close Test Runner.
You can view the test results in the testing center in Microsoft Test Manager. For more information, see How to: View Test Results Using Microsoft Test Manager
See Also
Tasks
How to: Change the Order of Test Cases in a Test Suite
How to: Create an Action Recording
How to: Use Shared Steps While Running a Test