Repeat a test with different data
When you write a manual test, you often want to specify that the test should be repeated several times with different test data. For example, if your users can add different quantities of a product to a shopping cart, then you want to check that a quantity of 200 works just as well as a quantity of 1.
To do this, you insert parameters in your test steps. Along with the test steps, you provide a table of parameter values.
You can also share parameters and their data between test cases when you use Team Web Access with Team Foundation Server 2015 or Visual Studio Online. That way you can run multiple test cases with the same data.
Convert existing parameters to shared parameters, so that you can use them and the associated data in other test cases.
After you have created a shared parameter set, open another test case and add the shared parameter set to that test case. You can search for the shared parameter set by name.
The shared parameter set is displayed in the Parameter values section after you add it. You can now use these parameters in your test case steps.
If the test case already has different parameter names for these shared parameters, map the shared parameter to the local parameter to use the shared parameter data.
When they are correctly mapped the data associated with the shared parameter will be displayed.
Add, edit and rename your shared parameter sets from the parameters tab. View the test cases that reference them in the test cases pane.
Each shared parameter set is a work item. From the Properties tab, you can view or make changes to this work item. For example, you can assign owners and track changes.
To update shared parameters, you must use Team Web Access.
When you run a test case with parameters, test runner shows the first row of parameter values.
When you’ve completed the steps, mark the test passed or failed.
Then go on to the next iteration of the test, which uses the next row of parameter values.
Some of the parameter values are wrong. Can I fix them without canceling the test?
Yes. Choose Edit from the context menu of the step.
If you marked any test iteration as failed, then the outcome of the whole test is shown as failed.
If you inspect the test results in Microsoft Test Manager, you can see the different results for each iteration:
It can be error-prone and tedious to work through a long table of parameter combinations. To speed things up, create an action recording when you run the test with the first set of parameter values, and then play it back for the other sets.
Select Create action recording before you press the Start button.
Complete the first test iteration and move on to the next.
Mark each step as passed or failed as you work. Enter parameter values in the application exactly as they are displayed in the test script.
Choose Play to run the test with the next set of parameter values.
Your actions will be played back automatically, but you still have to verify the results.
Record/playback doesn’t work with all applications. For details, see Supported Configurations and Platforms for Coded UI Tests and Action Recordings.