jmeter Feature Summary

I. Introduction

  jmeter mainstream performance testing tools, because of its open source, small file size, support for multiple protocols, etc., have become increasingly popular software test engineer. In this paper, a brief summary of the function of jmeter.

Two, jmeter tool part

  • Resource Builder: Resource testing server code generation, machine load (corresponding to the LR VuGen to)
  • User runner: usually a script engine, designated according to the script requires the user to simulate the behavior (LR equivalent of Controller)
  • Report Generator: The test report data in real-time, provides a visual display of data (corresponding to the LR Analysis)
  • Load Generator: used to generate load, usually in multi-threaded mode or multi-process simulation user behavior (equivalent to the LR Load Generators)

Brief three test tree

1.Test Plan (Test Plan)

  It is used to describe a performance test, comprising all the functions related to this performance test. Simply put, all the contents of this performance test is based on a plan. (Equivalent to a test scenario in LR)

Difference 2.Thread Group (thread groups) of

  • setUp Thread Group: A special type of Thread Group, may be used to perform pre-test operation. The behavior of these threads like a normal thread group elements. The difference is that these types of threads perform regular thread group before test execution. Similar LR's init ()
  • tearDown Thread Group: A special type of Thread Group, may be used to perform the test operation. The behavior of these threads would like a completely normal thread group elements. The difference is that these types of threads for execution on a regular basis thread group after the test. LR is similar in the end ()
  • Thread Group: We usually add a running thread. Can be seen as a virtual user groups, each thread in the thread group can be understood as a virtual user. The number of threads contained in the thread group will not change occurs during test execution, similar to the LR of action ()

3.Test Fragment (test sequences)

  Test element segment is a special thread group on the controller, and in the test tree hierarchy in a thread group, but not executed. Unless it is only to be executed when a referenced module or controller by the controller.

4.Config Element (Configuration element)

  To provide support for static data configuration. The CSV Data Set Config local data files may be formed Data Pool (Pool Data)

5.Timer (timer)

  Is provided between the waiting time for operation, the waiting time is commonly used in the performance test means the control of the client QPS. LR is similar to the "think time." jmeter defines different types of Bean Shell Timer, Constant Throughput Timer, fixed timers Timer

  QPS (QueriesPerSecond): means "query per second rate", is a server capable of the appropriate number of queries per second, is a measure of a particular query server within the specified time how much of the processing flow.

6.Per Processors (preprocessor)

  A request for the forthcoming issue of special treatment before the actual request is issued. For example, HTTP URL rewriting repair operators can implement URL rewriting. When the URL information of the session with a sessionID a class may be issued an actual request by the processor sessionID filling

7.Post Processors (post processor)

  After a request for a server response to obtain Sampler process. Generally used to extract specific data response (LR is similar to the concept of association)

8.Assertions (assertion)

  Assertion checking whether the test response data and the like obtained as expected, in general assertion for checkpointing to ensure data exchange performance testing whether the expected consistency

9.Listener (listeners)

  The test results for a series of data processing and visualization elements shown. For example graphical results, view reports the result tree and the polymerization

  PS: This is not a listener listening to the system resource element

 jmeter There are two types of control: Sampler (sampler) and Logic Controller (Logic Controller)

10.Sampler (sampler)

  Sampler (sampler) is the performance test sends a request to the server response information and recording the response time of the minimum unit. jmeter native support for a variety of different sampler, such as HTTP Request Sampler, FTP Request Sampler, TCP Request Sampler, JDBC Request Sampler and the like, each different type of sampler may emit different types of requests to the server according to the parameters set

11.Logic Controller (Logic Controller)

  Element comprises a Class 2, Class 1 for controlling a logical sequence transmission request Test Plan seed sampler node controller, commonly used if the controller, switch Controller, Runtime Controller, loop controllers. Another class 1 may control the sampler for organizing nodes, such as the transaction controller, the throughput of the controller

  

  

  

Guess you like

Origin www.cnblogs.com/huainanhai/p/12129603.html