How to: Run Manual Tests
Running manual tests using Test Runner can help you identify problems in your application. 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 a manual test that is ready for use. Before you run a manual test, you must first create a manual test. For more information, see How to: Create a Manual Test Case.
For more information about keyboard shortcuts to use when you run a manual test, see Keyboard Shortcuts for Microsoft Test Manager.
To run a manual test
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.
On the center group switcher, click the down-arrow and then click Testing Center.
In 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 either the test plan or the test suite listed under the test plan containing the test that you want to run.
You can click Filter to help you search for test matching. You can use the Tester drop-down list box to filter by to whom tests are assigned, or you can filter by Configurations.
The right side pane displays the test cases within the selected test suite.
When you run the tests from the test suite, the tests will be listed in Test Runner in the order 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.
Click the test case and then click Run.
Select Run with options to specify a build to run the test on, or to override the test settings and environment settings for the test plan. For more information about this, see How to: Override Settings in Your Test Plan For Test Runs.
Test Runner opens.
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 complete the installation, you will be prompted to restart your computer 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 clear and click Start Test.
You can increase the speed and efficiency of tests using action recordings. For more information about how to use the Create action recording option, see How to: Create an Action Recording.
If you have configured test settings to create an action log for the test being run, selecting the Create action recording option will use the settings that you configured. If you did not configure the actions diagnostic data adapter in your test settings, then the default values are used to create your action recording. For more information, see How to: Record User Interface Actions for Manual Tests Using Test Settings.
If your test setting includes collecting IntelliTrace data, you must start the application after the tests are loaded in Test Runner. For more information, see How to: Collect IntelliTrace Data to Help Debug Difficult Issues.
Perform the steps in the test.
If any 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 can optionally perform the following tasks provided by the toolbar in Test Runner.
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 using Reset and start the test over 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 create a bug 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 using Create exploratory bug. Submitting an exploratory bug in this manner allows you to 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 screenshot
To help clarify issues discovered during a test, you can optionally include screenshots while you are testing an application 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 optionally include comments to provide details and useful information that you discover 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 optionally attach a file associated with the application you are testing, 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 environmental snapshot
If you are running your test using a virtual environment, you can optionally attach a snapshot of the environment while you are performing a test using Take environment snapshot. Fore 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 arrow next to the active icon (with a blue vertical line) to the right of the test step and then click either Pass or Fail.
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 following global shortcut keys to mark a test step without changing the input focus from the application under test:
Pass test step: Win+Ctrl+Q
Fail test step: Win+Ctrl+W
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 testing, click End Test.
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.