In order to emulate users and think time correctly, you should consider inserting test actions before certain requests instead of using the Uniform Random Timer at the top of your test plan. In simple scripts, the master Uniform Random Timer may work just fine. This methodology will insert the specified delay before every single request in your thread group:
However, there are frequent cases where you don't want to insert delays between certain requests. For example, let's say you click a product and an additional request is made in order to load the product grid. The user will most likely think and browse before selecting the product, but the product grid should load immediately following the first request. The only delay here is dependent on the client-side response time. In this case, it's best to use a test action.
In the image below, you can see how the think time is placed in a Test Action before the simple controller containing the request for the product and product grid:
The think time is generated with the random variable (in this case it will fall between 5000 and 10000 ms). The random variable is then placed inside a property with the name "thinkTime." This property can then be defined in the test setup in the Dynatrace Load portal in case the think time needs to be adjusted during the test.
9 People are following this .