Jmeter Learning Journey (2) - Overview of Jmeter Functions

Note: The content is from books and the Internet, and is infringed and deleted. (If there is an error due to improper understanding, criticism and correction are welcome)


 1. Composition of Jmeter tools

  • Resource generator: generate the resource code of the server and load machine during the test process
  • User runner: usually a script running engine that simulates specified user behavior according to script requirements
  • Report Builder: Generate reports based on real-time data in the test, and provide a visual data display method
  • Load generator: used to generate load, often simulating user behavior in a multi-threaded/multi-process manner

  Test Plan: It is used to describe a performance test, including all functions related to this performance test. That is, all content of this performance test is based on a plan.

2. Threads (Users) thread users

  1. setUp Thread Group: A special type of Thread Group that can be used to perform pre-test operations. Threads of this type perform periodic thread group executions before executing tests. Similar to LR's init().
  2. tearDown Thread Group: A special type of Thread Group that can be used to perform post-test actions. This type of thread executes a periodic group of threads after the execution of the test. Similar to LR's end().
  3. Thread Group: We usually add running threads, which can be seen as a virtual user group. The number of threads contained in a thread group does not change during test execution. Similar to LR's action().

3. Test Fragment

  This element is a special thread group on the controller, at the same level as the thread group in the test tree. Executed when it is a module controller or is referenced by a controller.

  

  The following are the eight types of executable elements of a thread group

 

Fourth, configure the original (Config Element)

  Used to provide support for static data configuration.

5. Timer

  Used to set the wait time between operations. Similar to LR's "think time".

6. Pre-processors (Per Processors)

  Used for special handling of upcoming requests before the actual request is made.

7. Post Processors

  It is used to process the server response obtained after Sampler sends a request. Typically used to extract specific data from a response. LR-like association concept.

8. Assertions

  Used to check whether the corresponding data obtained in the test is as expected. It is generally used to set checkpoints to ensure that data interaction during performance testing is consistent with expectations.

9. Listener

  A set of components used to process and visualize test result data.

10. Sampler

  It is the smallest unit for sending a request to the server, recording the response information, and recording the response time in the performance test. Jmeter natively supports a variety of different samplers, and each type of sampler can send different types of requests to the server according to the set parameters.

11. Logic Controller

  It includes two types of components: one is a controller used to control the logical sequence of requests sent by the sampler node in the test plan, commonly used are If controller, loop controller, etc.; the other is used to organize controllable sampler nodes, Such as transaction controller, throughput controller, etc.

  

 

Guess you like

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