Migrating Manual Tests from Versions of Visual Studio Prior to 2010
Using Visual Studio Premium or Visual Studio Test Professional you can create manual test cases as work items in your team project. You can enter the required test steps, and any other information that you have to have in order to run the manual test, as part of the work item. This includes attaching files to the manual test case. For more information about this new manual test case, see Creating Manual Test Cases.
If you have existing manual test cases that you created by using versions of Visual Studio prior to Visual Studio 2010, you can migrate data from these test cases into a manual test case using Microsoft Test Manager. To use a power tool to migrate test cases from earlier versions of Visual Studio, see the following Microsoft Web site.
You can also share a set of common test steps between multiple test cases. These common test steps are called shared steps. This simplifies maintenance of test steps if your application under test changes.
Any test case that you create is associated with your team project and can be added to multiple test suites. The test suites can be in the same or in different test plans. When you run these test cases, you can mark which test steps pass and which steps fail. You can create a bug from a test case that fails. This bug automatically includes the test steps and other information that was collected.
You can create a manual test case from within a test plan by selecting a suite, as shown in the following illustration:
If you created the test suite by adding a requirement to the test plan, any existing test cases or new test cases that you add to the test suite will automatically be linked to the requirement.
You can then add the details for your test case, as shown in the following illustration. You can copy the title from your existing test case into this new manual test case. You can also copy any test details or description of the test into the Summary tab.
To add test steps, select the steps from your manual test file in your solution and copy them to a Microsoft Word or an Microsoft Excel document. You can also copy to a text document. The formats for the documents that make it easy to copy the steps are shown in the following illustration.
You can also use a power tool to help you convert any of your existing test cases from Microsoft Excel. To access the power tool, use this Microsoft Web site.
If you copy both actions and expected results from Microsoft Word or a text document, then the lists of each pairing of an action with an expected result must be tab-delimited.
For more detailed steps about how to do this, see How to: Add Test Steps to a Manual Test Case from a Microsoft Excel or Microsoft Word Document.