LoadRunner description of each option when parameterized

loadrunner Description of each option when parameterizedCategory: LoadRunner 2009-03-27 09:32 6294 People read Comments (1) favorite reports Loadrunnerrandomgeneratoreach script File

Data files can be created successfully by creating table and data wizards, and operators are free to choose the way they are accustomed to. In short, you can stick to the data file on the principle of data, there will be no problem.

When you go back to the Parameter Properties page, you find that the data is ready, and the original gray area is now available.

Select Next line has the following options:

Sequential:

Reads in a row of rows sequentially. Each virtual user will be read in the same order.

Random:

Any choice. But in each iteration, there will be no change.

Unique:

The only number. When you use this option, you need to ensure that there is enough data in the prepared data file. For example, to do 20 virtual users, each user to do 5 iterations, the first user in 5 iterations of the data file in the data 1~ data 5, the second user in 5 iterations using data in the data file 6~ data 10, and then 20 users will use 100 data. It is important to ensure that there are more than 100 data in the prepared data file, otherwise the runtime will have an error.

Same line as a parameter:

and the previously defined parameters fetch the records of the peers. It is usually used in relational data. For example, when I do the parameterization of the login password, because it is related to the UserID, it will use this choice.

"Time to update values" has the following options:

Each iteration:

Updates a new value for each iteration.

Each occurrence:

Updates a new value whenever the parameter is present.

Once

The value of the parameter remains constant regardless of the number of iterations.

NOTE * * *

1. Parameter type:

When I created the parameters, I chose the parameter type as file. There are 9 kinds of parameter types, so let's take a brief look at all the parameter types and meanings.

1.1. DateTime:

You can substitute a datetime type where you want to enter a date/time. Its property settings are also simple, select a format. Of course, you can also customize the format.

1.2. Group Name:

Seldom used. In practice, LoadRunner uses the VUser Group that the virtual user resides in instead. However, when running in Vugen, the Group name will be none.

1.3. Load Generator Name:

In practice, LoadRunner uses the machine name of the loadgenerator that the virtual user resides in instead.

1.4, Iteration Number:

In practice, LoadRunner uses the number of times that the test script is currently looping instead.

1.5. Random Number:

Random number. Very simple. You can set the range that produces the random number in the property settings.

1.6. Unique Number:

The only number. You can set the size of the first number and the number of increments in the property settings. Note: Use this parameter type to be aware of the maximum number that can be accepted. For example, the maximum number that a text box can accept is 99. When the parameter type is used, the first number is set to 1 and the increment is 1, but when 100 virtual users run concurrently, the 100th virtual user enters 100, so the script runs with an error. This increment means that each user takes the increment of the first value, and the difference between the two loops adjacent to each user is 1. Example: If the starting number is 1, increment to 5, then the first user first cycle to the value of 1, the second cycle to the value of 2; the second user first loops with a value of 6, the second is 7, and so on.

1.7. VUser ID:

Setup is simple. In practice, LoadRunner uses the ID of the virtual user instead, which is controlled by the controller. However, when running in Vugen, the VUser ID will be –1.

1.8. File:

You need to edit the file in the property settings, add the content, or fetch the data from the out-of-the-box database (that's the type I'm using).

1.9. User Defined Function:

Extracts data from a user-developed DLL file.

Detailed settings for the various parameter type properties are not introduced here, so you can take a look at the Help documentation when you use it.

LoadRunner description of each option when parameterized