The JMeter test plan has an option called the "function test mode", which , if selected, causes the JMeter to record every sampled data returned from the server. If you select a file in the test listener, the data will be written to the file. This is useful if you try a smaller test to ensure that the JMeter is configured correctly and that your server is returning the desired results. The consequence of this is that the file will grow rapidly and the efficiency of the jmeter will be affected.
If you do not log data to a file, this option is no different.
- Thread Group: Is the starting point for any test plan, and all logical controllers and samplers must be placed under the thread group. Other test elements, such as listeners, can be placed directly under the test plan, which takes effect for all thread groups. Thread groups are used to manage the jmeter threads required to perform performance tests. Users through the thread Group's control panel can:
- Set the number of threads
- Set Thread start cycle
- Set the number of cycles to execute a test script
- Scheduler options--can set start time, end time, duration, and startup delay, note that startup delay will invalidate the startup time, and the duration will invalidate the end time
- Controller: JMeter There are two types of controllers: the sampler and the logic controller, which together drive the test process. The sampler is used by JMeter to send requests to the server. The user can use a logical controller to control JMeter's test logic, such as when to send a request
Sampler to tell JMeter to send a request to the specified server and wait for the server to request it. The sampler executes in the order in which it is in the test tree and can use a logical controller to change the number of times the sampler is running.
-
- FTP Request
- HTTP Request
- JDBC Request
- LDAP Request
- Java Object Request
- Soap/xml-rpc Request
- WebService (SOAP) Request
- Logic controller: Helps users control the test logic of jmeter, especially when sending requests, the logic controller can change the order of request execution of its sub-test elements
- Listener: Provides access to the information that JMeter collects during the test, and the graph results listener draws the system response time in a picture, the view result tree listener shows the details of the sampler request and response, as well as the underlying part of the system response in HTML and XML format
- Timer: Causes each sampler in the scope to wait for a fixed length of time before execution. To add a pause to a location in a test plan, you can use the "Test Action" Sampler
- Assertion: Checks the response received from the server, such as adding an assertion for an HTTP request, to detect the text "". To view the assertion results, add an assertion result to the thread group to listen to it, and the failed assertion will be displayed in both the view results tree and the view results with tables listener
- Configure components: closely associated with the sampler, add or modify requests, configure components not to send requests, configure the component "user-defined parameters" to be executed at the initial stage of the test (regardless of where it is in the test tree)
- Pre-processor: a special operation before a request is made, often used to modify some of the sampler's settings before the sampler makes a request, or to update the values of some variables
- Post Processor: After the sampler makes a request to do some special operations, often used to process the server's response data. Extracts data from the server response data.
JMeter Study Notes--jmeter Common test elements
