Thread group)
A: Setup thread group
A special type of threadgroup that can be used to perform pre-test operations. These threads act like a normal thread group component. The difference is that these types of threads perform regular thread group execution before testing.
B: teardown thread group
A special type of threadgroup that can be used to perform post-test actions. These threads act like a normal thread group component. The difference is that these types of threads execute regular thread groups after testing.
C: thread group
Number of threads:
Number of virtual users. A virtual user occupies a process or thread. Set the number of virtual users here, that is, set the number of threads.
Preparation duration (ramp-up period (in seconds ):
How long does it take to set the number of virtual users to start. If the number of threads is 20 and the preparation duration is 10, it takes 10 seconds to start 20 threads. That is, two threads are started every second.
Cycles:
The number of requests sent by each thread. If the number of threads is 20 and the number of loops is 100, each thread sends 100 requests. The total number of requests is 20*100 = 2000. If "forever" is selected, all threads will send requests until the script is stopped.
Test Fragment)
The test snippet is a new option added after version 2.5.
The test fragment element is a special thread group on the controller. It is in a level with the thread group on the test tree. It is different from a thread group because it is not executed unless it is a module controller or is referenced by a controller.
Config Element)
Config element is used to support static data configuration. CSV Data Set config can form a data pool for local data files, but does not support configuration of HTTP request sampler, TCP request sampler, and other types.
You can modify the default data of sampler. (For example, HTTP cookie manager can be used to manage HTTP request sampler cookies)
Timer (timer)
The timer (timer) is used to set the wait time between operations. The wait time is a commonly used hand end for controlling the client QPS in performance testing. Similar to the "thinking time" in LoadRunner ". Jmeter defines bean shell timer, constant throughput timer, fixed
Timer and other different types of timer.
Constant throughput timer (constant throughput timer)
QPS: Query per second query rate. The number of queries that a query server can process per second. On the Internet, the performance of machines serving as Domain Name System servers is often measured by the query rate per second.
Preprocessor (per processors)
It is used to process the request to be sent before the actual request is sent. For example, you can use the http url rewriting fix to rewrite the URL. When rul contains session information such as sessionid, you can use this processor to fill in the actual sessionid of the request.
Post Processors)
It is used to process the server response after the sampler sends a request. It is generally used to extract specific data in the response (similar to the association concept in the LoadRunner test tool ). For example, XPath extractor can be used to extract the number of response data obtained by the given XPath value.
Data.
Assertions)
Assertions are used to check whether the data obtained in the test meets expectations. assertions are generally used to set checkpoints to ensure that the data interaction during the performance test is consistent with expectations.
Listener (listener)
This listener is not a component used to listen to system resources. It is a series of components used to process and visualize the test result data. Graph row result, view result tree, and aggregate report. These are all frequently used components.
Detailed parameters of aggregate reports
Sampler for jmeter, sampler is a unit of interaction with the server. HTTP Request