Parameterized user parameters
Why use parameterization: Because the parameterization method is not used, the data changes too much, and the http values are manually modified one by one. This is a lot of work and difficult to maintain
The benefit of parameterization: when 10 HTTPs all use the same parameter, when I go to change the value of this parameter. The parameters of 10 http requests will also be changed together; easy maintenance
The disadvantage of the user parameter is that it is not suitable for a very large range of values; Csv data set config will be discussed later, which is suitable for a large range of values.
1. Example diagram of user parameter adding process
2. User parameters Manually input parameters, see the text description in the figure below
3. Message body/parameter input method: ${name} name is the name in the user parameter
I was also confused about the difference between the user parameters in the preprocessor and the user-defined variables in the configuration element. After running it many times, I got a little insight.
User parameters in the preprocessor (for each reference)
1. The option to update once per iteration is checked, whether it is multi-threading or multi-loop, each time the same thread group is run or in a single loop, it will not be updated each time the user parameters are referenced and called (the first one is used). User parameter value called by a reference), it will be updated once in different thread groups or
in different loops is updated every time a user parameter is referenced and called in
User-defined variables in the configuration element: whether it is multi-threading or multi-loop, the same variable value is used when each thread group is referenced (the user variable value at the first reference), but the configuration element is executed in Jmeter The highest priority, higher than the preprocessor.