Load Test-Jmeter
I came across Apache Jmeter when I was researching load testing within the scope of the project I was involved in. I prefer Jmeter to create loads with ease of interface and a high number of users.
If you are a Postman user, you can also choose Postman Runner for load testing. I could not continue to use it because I observed that it was slower than Jmeter and could not create the load I was aiming for.
What is load testing and why is it needed?
It is a type of test that helps to observe how the application will behave when many users access the application at the same time.
For example, It is the system’s reaction to this situation when many different users come to the system at that moment, in scenarios such as instant discount, special day, or announcement with push notification of a project that does not cause any errors in its normal flow. In order for the system not to be able to handle this situation and not to cause interruptions/errors, load tests are required in order to provide controls and observe the system's upper limits and produce solutions accordingly.
What is Jmeter and how does it work?
JMeter is a tool that simulates a group of users sending requests to a target server and provides graphical diagrams of the target server’s statistical information.
Opensource is a Java applet. Originally designed for testing web applications, it has been extended to other testing functions as well.
User requests to servers while using an application are simulated with JMeter as if real users were requesting these resources.
The simulated user scenarios can be configured as if more than one user is running the same scenario at the same time by differentiating the requests to the application, and a load of the desired size can be created on the system.
Installation is quite simple. Let me explain the Windows installation and general usage features with a few examples;
It is necessary to download the tar.gz file format from the URL and run the JMeter batch file in the /bin directory.
The Jmeter splash screen starts as a “Test Plan”.
Thread Group:
Number Of Threads: The field where we specify the number of users we want to load.
Ram-Up Period: This is the field where the number of seconds to reach the specified number of users is specified.
Startup Delay: The field specifies how long to wait to start sending the request.
Http Request:
It is the structure in which the URL or ip-port based endpoint is created for the endpoint to be requested.
View Result Tree:
It is the structure where the test results can be observed as success-fail, and the request-response outputs are included and controlled.
