JMeter – Config Element
When the script execution starts, the JMeter Configuration Element or Configuration Element sets the start configuration of a test. You could also say that configuration components perform pre-execution tasks before executing a test. Configuration items are used to configure variables and default settings used by other test components such as the sampler etc.
Configuration components have a defined scope. So you can declare them both globally and locally. If they are defined in a sampler, then that sampler first processes them in the same scope and they can only be used by that sampler; they are not accessible to other samplers or external elements.
Take a look at the scope-flow diagram below:
There are three configuration elements listed in the scope-flow diagram above. They are:
1.G1: Any thread operating under the same test plan may access this global configuration element. Hence Both samples 01 and 02 have access to the G1 configuration element.
2.L1: This local configuration element only affects the Thread Group 01 element. Hence Sampler 02 is unable to access it, although Sampler 01 can.
3.L2: This local configuration element only affects the Thread Group 02 element. Hence Sampler 01 is unable to access it, however Sampler 02 can.
Possible Parent element(s) of Config Element:
- Test Plan
- Thread Group
- Test Fragment
- Sampler
- Logic Controller
Possible Child Element(s):
- NA
