1. The test plan is the starting point for testing using JMeter, which is a container for other JMeter test elements.
2. The thread group represents a certain number of concurrent users, which can be used to impersonate concurrent users to send requests. The actual request content is defined in sampler, which is contained by the thread group.
3. The listener is responsible for collecting the test results and is also informed of the way the results are displayed.
4. Logic controllers can customize the behavior logic of the JMeter send request, which is used in conjunction with sampler to simulate complex request sequences.
5. Assertions can be used to determine whether the result of a request response is as expected by the user. It can be used to isolate the problem domain, i.e. to perform a stress test if the function is correct. This restriction is very useful for effective testing.
6. Configure the components to maintain sampler required configuration information, and modify the requested content according to the actual needs.
7. The predecessor processor and the post processor are responsible for completing the work before and after generating the request. The predecessor processor is often used to modify the requested settings, and the post processor is often used to process the response data.
8. The timer is responsible for defining the delay interval between requests.
The use of JMeter is very easy, and the article using JMeter on onjava.com provides a very good introduction.
Drizzle study Note: JMeter's main test component summary