Runner Keeps only Used and Distinct Parameter from the Parameter-Values
It is possible that the parameter values found during the parameter resolution search may contain more parameters than are needed for the current test case. This is likely if the parameter source is shared between several test cases.
When this happens, the parameter resolution algorithm ignores and removes the irrelevant values and maintains the unique values in order to avoid duplicated runs of a test case with the same parameters.
For example, consider a test case that is using a ${fruit}, parameter and the parameter values are found are in this table:
|
Fruit
|
City
|
Price
|
|
banana
|
Stuttgart
|
10
|
|
banana
|
Budapest
|
5
|
Because the city and price parameters are unused in this test case, they do not appear in the current test case. These parameters and values are dropped from the parameter set and only two rows remain, both having the fruit=banana value. If we run that the test case with those values, the same test would be run twice with same parameter. To avoid this, only the unique parameters set combinations are kept. This works the same way as SQL's SELECT DISTINCT statement.