You can run a parameterized test in two ways:
-
Run the single parameterized test. To do this, go to Test Management > Test Library, move the mouse cursor over the parameterized test, then click the Run button that appears to the left.
-
Add the parameterized test to a test set and run the test set on the Test Sets screen.
The Test Runner creates a test instance for each row of values found in the associated file with parameter values. In our example, there are three value pairs that will be tested.
Click the image to enlarge it.
Click a test to run it.
When you run the test or a test set, the Test Runner will automatically replace parameter names in steps with values from the attached CSV file.
Click the image to enlarge it.
Step through your test run, passing or failing each step, and post your actual results. When you reach the next test, it will display the values from the next row of your CSV file that contains parameter values.
Missing Values
If your test contains parameters in the steps or expected results, but you do not have a parameter value CSV file attached, or the attached file is missing, or several values in the file are missing, you can still run the test. In that case, you will see the formatted parameter names during the test run. You can edit the test step and manually enter the desired value as you run the test.
Click the image to enlarge it.
Notes:
-
You can edit parameterized tests during the test run, but changes will not be pushed to the Test Library. Therefore, the original test will not be updated.
-
A test can have only one CSV file with parameter values attached. If you need to make any changes to it, remove the existing CSV file from the Token Values tab of the test form in the Test Library and upload a modified one.
-
Parameter names can include only digits and lower-case or upper-case Latin characters. Special symbols, national characters, and punctuation marks are not allowed.
-
If any of the Description or Expected Result fields of the steps contains a parameter (that is, any value stored in the
[?parametername]format), the system considers the test as parameterized. All tests of that type are flagged as parameterized in the system-controlled Is Tokenized? check box. You can use this to filter and search for parameterized tests in the Test Library.