PERFORMANCE TESTING
What’s the Performance testing ?
Hi, in this article I will give some information about performance tests. Performance testing is a test to check whether the system meets the specified expectations in certain situations. Performance testing does not aim to find bugs in the system, but reveals bottlenecks in the system.
To mention a few purposes of performance testing: Increases in system traffic; To monitor how it affects transaction time and security, to see which user level performance problems will occur. The decrease in performance levels is done to determine which component of the system is causing it and to understand how the system behaves under normal conditions.
Types of Performance Testing
Load test : Checks the performance of the application under expected user loads. The goal is to identify performance bottlenecks before the app is released.
Stress testing : It involves testing the application under extreme workloads to see how it handles high traffic or data processing. The goal is to determine the break point of the application.
Endurance test : It is done to make sure that the application can handle the expected load for a long time.
Spike test : Tests the application’s response to large spikes in user-generated load.
Volume testing : Data is placed in a (High-dimensional) database and the behavior of the overall software system is monitored. The goal is to check the performance of the software application under varying database volumes.
Scalability testing : The purpose of scalability testing is to determine the effectiveness of the software application at “scaling” to support the increase in user load. The software helps you plan to add capacity to your system.
Performance Testing Process
The methodology applied for performance testing can vary greatly, but the purpose of performance testing is the same. It can help demonstrate that your software system meets certain predefined performance criteria. Or it can help compare the performance of two software systems. It can also help you identify parts of your software system that are degrading its performance.
Below are the titles of the processes on how to perform the performance test.
- Define your test environment
- Set performance acceptance criteria
- Plan and design performance tests
- Configuring the test environment
- Implement the test design
- Run the tests
- Analyze, tune and retest
The basic parameters monitored during performance testing include:
Processor Usage, Memory use, Disk time, Bandwidth, Private bytes, Committed memory, Memory pages/second Page faults/second, CPU interrupts per second, Disk queue length, Network output queue length, Network bytes total per second, Response time
Let’s experiment with jmeter :
After running Jmeter, we need to right-click on the test plan section and select the Thread Group option.
We will add a logic controller to the thread, select Simple Controller from the logic controller tab. In the created part, we add an http response on which we will test.In the http request section, we enter the information of the site we will test. Protocol , server name etc.
To view the results, right click on Thread and select Listener -> View Result Tree.
We can enter the number of users and the number of cycles in which the test should be performed in the Properties field in the Thread section.
Let’s start the test… :)
We will make a get request to the site we selected.
When we look at the view result tree, we see the response time vs. the definitions.
Now, we will test our request call with its working in embedded parts of the site, that is, the loading times of the images on the site will be included in our test.
When we look at the results, we can see how much the load time has increased. The example in Jmeter has been here so far, I will add the link of the source I learned, you can continue here…