CheatSheet: Basic structure and elements of a JMeter Test Plan

This blog post contains an overview, where we get a summary of the used elements of JMeter for the Example Functional Performance Test.

1. Test plan

Test Plan is a JMeter project. (Definition from the user-manual)

2. Thread Group

Thread Group can define a Group of Users with the same behavior. In our case, we will invoke only one HTTP endpoint.

3. Config Elements

The Config Elements up defaults and variables for the usage of Sampler in our HTTP Request.

3.1. User Defined Variables

We will use the User Defined Variables later and use them in combination with User Parameters. It is essential to understand that User Variables are only available in the hierarchy structure level of Test Plan, and Parameters are available in the entire Test Plan.

3.2. Counter

We use the Counter in a loop to access the current loop count.

3.3. CSV Data Set Config

We use the CSV Data Set Config to add the CSV file input to the Loop Controller for various invocation variations for the HTTP request payload.

3.4. Header Manager

We use the Header Manager to add the Header Basic Authentication to our HTTP request later.

4. Logic Controllers` and Loop Controller

The Logic Controllers contains the Loop Controller we going to use to loop the CSV file input for various invocations of the HTTP request payload.

5. Samplers

Samplers are used to create requests and wait for responses.

5.1 HTTP Request

HTTP Request is a part of a Sampler.

We use the HTTP Request to create test results.

5.2 JSR223_Sampler

The JSR223_Sampler can be used to set properties or variables. In the example, we use it to create our own CSV file.

6. Assertions, Response Assertion, and JSON Assertion

The Assertions contain the verification points we can define to inspect the response and the response values in our case in a JSON format.

7. Pre Processors and JSR223 PreProcessor

We use the Pre Processors to modify the Samplers in our case, for example, to prepare the HTTP basic authentication. In our case, we use the JSR223 PreProcessor with groovy scripting to implement a custom behavior.

8. Post Processors

We use the Post Processors to modify information after the execution of a Samplers in our case. For example, we write a custom log in addition to the logs of JMeter. Therefore, we use the JSR223 PostProcessor.


I hope this was useful for you and let’s see what’s next?

Greetings,

Thomas

#jmeter, #performancetest, #cheatsheet

One thought on “CheatSheet: Basic structure and elements of a JMeter Test Plan

Add yours

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Blog at WordPress.com.

Up ↑