Open the old version Jmeter page: + bench including test plan.
The new version of the open Jmeter page: + bench including test plan.
JMeter There are two types of control: the sampler (sample) and a logic controller (Logic Controller), these originals to drive a test process.
1, Test Plan (Test Plan) : used to describe a performance test that contains all the functions related to this performance testing. Also said that all the contents of this performance test is based on a plan.
2, Threads (Users) Users Thread
Test Plan> Threads> Thread Group
jmeter3.0 version, the default thread group setUp theread Group and terDown Thread Group, thread group. Other thread group downloadable plug-ins.
1) setup thread group
A special type of ThreadGroup, may be used to perform pre-test operation. The behavior of these threads exactly like a normal thread group elements. The difference is that these types of threads perform regular thread group before test execution.
setUp Thread Group similar to the init loadrunner may be used to perform pre-test operation.
2) teardown thread group.
A special type of ThreadGroup, may be used to perform the test operation. The behavior of these threads exactly like a normal thread group elements. The difference is that the thread group to perform on a regular basis after the end of these types of threads execute the test.
tearDown Thread Group End of similar loadrunner. may be used to perform the test operation.
3) thread group (thread group).
This is what we usually add a running thread. Popular speaking group ,, a 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 in the thread group is not included in the change during test execution.
3, the sampler (Sampler)
Thread Group> Sampler
Sampler (Sampler) is a performance test to the server sends a request, recording in response to information recording minimum unit response time, the JMeter native support many different Sampler, such as HTTP Request Sampler, FTP Request Sampler, TCP Request Sampler, JDBC Request Sampler etc., each different type of sampler may emit different types of requests to the server according to the parameters set.
In all Sampler Jmeter in, Java Request Sampler and BeanShell Requst Sampler are two special customizable Sampler.
4, the logic controller (Logic Controller)
Thread group> logic controller
Logic controller, comprising two elements, one is the logic for controlling the test sequence transmission request sampler node controller in plan, if there are commonly used (If) controller, switch Controller, Runtime Controller, loop controllers. Another type of tissue is used to control the sampler may be nodes, such as the transaction controller, the controller throughput.
5, element configuration (Config Element)
Thread Group> configuration element
Element configuration (config element) for providing data for static configuration. CSV Data Set config file can form a data pool of local data (Data Pool), corresponding to the HTTP Request Sampler TCP Request Sampler and other types of non-member can be formulated to modify the default data Sampler.
http corresponding HTTP header information manager, HTTP Request Defaults
6, timer (Timer)
Thread Group> Timer (Timer)
Timer (the Timer) for setting a waiting time between operations, the waiting time is commonly used in the performance test means the control of the client QPS. Similar LoadRunner inside the "think time." JMeter defines different types of Bean Shell Timer, Constant Throughput Timer, fixed timers Timer.
7, pre-processor (Per Processors)
Thread Group> preprocessor
A request pre-processor for the upcoming special treatment given before the actual request is issued.
8, the post processor (Post Processors)
Thread group> postprocessor
Post-processor for post request to the server in response to obtained processed Sampler
9, assertion (Assertions)
Thread Group> assertion
Assertion checking whether the respective test data and the like obtained as expected, in general assertion for checkpointing to guarantee that the data interaction during the performance testing as expected. Common response to the assertion
10, the listener (Listener)
Thread Group> Listener
This test is used to monitor the results of a series of data processing and visualization elements shown. Graphical results, view the results tree, polymerization report, look at the table with the results we are frequently used elements.
