Part 3: Scope and execution order of jmeter

1. The scope of the element:

8 types of executable components, testplan and threadgroup are not executable components; among these components, the sampler is a typical component that does not interact with other components, and the logic controller is only valid for the samplers of its child nodes. And other elements (configuration elements, timers, assertions, listeners,) need to interact with elements such as samplers;

The scope of components in jmeter is determined by the parent-child relationship of components in the tree structure of the test plan. The principles of scope are:

Sampler: The component does not interact with other components, so: there is no scope problem;

Logic controller: only works for the sampler and logic control in its child nodes;

In addition to samplers and logic controllers, other 6 types of components, if it is a child node of a sampler, the component acts on its parent and child nodes, and if its parent node is not a sampler, its scope is the component All other descendant nodes under the parent node (including child nodes of child nodes of child nodes, etc.)

 

2. The order of element execution:

Configuration element---preprocessing---timer---sampler---postprocessor---assertion---listener;

The above order: There are two points to note:

pre-, post-processors and assertions, if there is no :sampler in their scope, they will not be executed;

If: there are multiple components of the same type in the same scope, these components are executed in the order in which they are in the test plan;

 

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325232727&siteId=291194637