How JMeter threads execute sequentially -- test plan configuration

1.Test Plan Check run each thread group independently

Default is unchecked , All threads are done at the same time , It will lead to business operations without logging in to the front thread .

User defined variables ：  User defined variables can be added to the test plan . Generally, add some common configuration of the system . If you want to switch the environment during the test , Switch configuration , It is generally not recommended to add variables to the test plan , Because it's not convenient to enable and disable , Generally, it is to directly add user-defined variable components . Such as ：

Run each thread group independently ：  Used to control the execution order of multiple thread groups in the test plan . Pictured above , Thread group 1 And thread groups 2 Threads of are executed in parallel , The execution sequence of the execution process thread is unpredictable .
If I check that ​​​ Run each thread group independently ​​, It can guarantee the thread group 1 The execution of must be in the thread group 2 Before , Thread group 1 completion of enforcement , To execute thread groups 2.

The execution order of the sampler in the thread group ：  The default is to execute from top to bottom . Alternate controller 、 Random controller 、 Random sequence controller and cycle controller can change the execution order of sampler .

Function test mode （Functional Testing）  If this option is selected , Monitoring components such as “ View the result tree ” The configuration is saved to a file , that jmeter The result of each request will be saved to a file . Generally, it is not recommended to check .

Run tearDown Thread Groups after shutdown of main threads：