Data allocation and Update method of LoadRunner test file/table parameters

When using LR as a test, it is very important to set the parameters and the different parameter settings directly affect the test results. Once searched for similar problems on forums and other websites, want to find out the actual operation of the process, but unfortunately, found mostly scattered, or did not see how to do, there is no way, just thought of the Handbook, a look below, only to find that the manual summed up as a preliminary guidance has more than enough. Here are some of the help files from the LR self.

Alert: After encountering problems, search on the internet, while searching the manual, do not need to ask questions, because you asked the others may not have met, or simply do not understand your meaning, even worse, put N days also no one cares.

For file and table type parameters, the selected data allocation method and update method together affect the value that VUser uses to replace the parameter during the scene or session step run.

The following table summarizes the values that VUser uses depending on the selected data allocation and update properties:

Example

Suppose the table/file includes the following values:

Kim;david; Michael; Jane; Ron; Alice; Ken; Julie; Fred

If you choose to assign data using the Sequential method:

If you choose to update every iteration, all vuser will use Kim for the first iteration, the second iteration using David, the third iteration using Michael, and so on.

If you choose to update every time you appear, all vuser will use Kim the first time they appear, using David for the second time, using Michael for the third time, and so on.

If you choose to update once, all VUser will use Kim in all iterations.

If there are not enough values in the datasheet, the Vugen returns to the first value in the table, and the loop continues until the test finishes.

If you choose to assign data using the Random method:

If you choose to update each iteration, VUser uses the random values in the table for each iteration.

If you choose to update every time you appear, VUser uses random values each time the parameter appears.

If you choose to update once, all

VUser will use the first randomly assigned value in all iterations.

If you choose to assign data using the unique method:

If you choose to update in each iteration, for a test run with 3 iterations, the first vuser will extract Kim on the first iteration, the second iteration fetch David, and the third iteration to extract Michael. The second vuser extracts Jane, Ron, and Alice. The third vuser extracts Ken, Julie, and Fred.

If you choose to update every time you appear, VUser uses the unique value of the list each time the parameter appears.

If you choose to update once, the first vuser will extract Kim at all iterations, and the second vuser will fetch David at all iterations, and so on.