Jmeter environment configuration and precautions (2)

1. Loops don't work: if loops are set in the test plan, they don't work, only in Step1.

two。 Using Badboy to record scripts, sometimes requests are not recorded, are exported as jmeter scripts, and an error is reported at runtime.

Using the Chrome browser, open F12, go through the business process again, and find the request that was missed by Badboy.

Add the request to the appropriate location

Run the entire script again, correct.

3. Scope and execution order of each component: the scope of the component is determined by the parent-child relationship of the component in the numerical structure of the test plan.

Within the same scope:

The components in the test plan are executed in the order from left to right in the figure above

If there are multiple components of the same type, they will be executed in the upper and lower order.

On the left side of the sampler:

Configuration components and controllers work on all components within their scope

The preprocessor and timer are executed before all sampler in their scope

On the right side of the sampler:

All three components execute after all sampler in their scope

4. Timer

Fixed timer:

Delays execution of all sampler in scope for a certain period of time, which is equivalent to thinking time

Synchronization timer:

That is, the rendezvous point, which is used in scenarios such as second kill.