Performance Testing : Types of Performance Testing
Performance testing and types of performance testing such as Load Testing, Volume Testing, Pressure Testing, Capacity Testing, Soak/Endurance Testing, and Spike Testing come under Non-functional Testing
In the Sphere of Software Testing, Testers mainly focus on Black Box and White Box Testing. Beneath the Black Box testing, again you will find different kinds of testing. The major types of testing are Functionality testing and Non-functional testing. Like I mentioned in the first paragraph of this guide, Performance testing and testing types associated with functionality testing fall below Non-functional testing.
In current market performance and responsiveness of applications play an important part. We conduct performance testing to deal with the bottlenecks of the machine and to fine tune the system by discovering the source of performance issues. Performance testing answers to the questions such as how many users that the machine could manage, How well the system could recover when the no. Of users crossed the maximum users, what’s the reaction time of this machine under normal and peak loads.
We use tools like HP LoadRunner, Apache JMeter, etc., to measure the performance of any Software or System Under Test (AUT). Let’s see what are these terms in detail below.
Types of Performance Testing:
Performance testing determines or validates the speed, scalability, or stability features of the system or application under test. Performance is concerned with achieving response times, throughput, and resource-utilisation degrees that meet the performance objectives for the project or product.
Capacity Testing:
Ability Testing is to determine how many users the system/application can manage successfully before the operation aims become unacceptable. This also lets us avoid the possible problems in future such as increased user base or increased quantity of information.
Load Testing will be to confirm that the system/application can manage the anticipated number of trades and to verify the system/application behaviour under the normal and peak load requirements.
Volume Testing:
Volume Testing is to verify that the system/application can manage a massive amount of information. This testing focuses on Data Base.
Stress Testing:
Stress Testing would be to confirm the behaviour of this system once the load increases more than the machine’s design expectations. This testing addresses which components fail first when we stress the system by employing the load past the design expectations. So that we can design stronger system.
Soak Testing:
Soak Testing is aka Endurance Testing. Running a system at high load for a lengthy period of time to recognise the performance issues is called Soak Testing. It’s to make certain the program can handle the expected load over a lengthy time period.
Spike Testing:
Spike Testing is to ascertain the behaviour of the machine under abrupt increase of load (a high number of users) on the computer system.
