Performance Testing

Performance Testing is the testing in which Test Team determine how the system will perform in terms of responsiveness and when the system will be overloaded. In Performance Testing , we validate or verify the scalability, reliability and how the system uses the available resources. These all are the quality attribute of the system.

Performance Testing is the non functional testing type. Performance Testing also determine the speed of the system. In Performance Testing we can check the response time of the system and compare the speed of the software with the other similar software and verify that the system matches the client requirement or not. In terms of speed it can check the bandwidth, data, transfer rate, throughput, efficiency and reliability.

Performance Testing is the part of Quality Assurance (QA) process.

Performance Testing Type

• Load Testing: Meaning of Load Testing is to provide constantly or steadily  load for a software to check that how software is responding in increasing load without significant performance degradation. Load Testing is put load over the system to check the response. We increase the limit until the threshold limit. In Load Testing we determine the system limit in normal load and peak load limit of the system.

• Stress Testing: Stress Testing is the testing to verify the response/output of the software beyond the breaking point of the system.  Stress Testing, test team focus on robustness, availability and the error handling under the heavy load rather then correct behavior under normal circumstances. It is the type of non functional testing.

• Soak Testing: In this testing, we provide the continues significant load for significant time to test the application. Suppose you are testing a function in 1 hour and then you testing the same function for 3 hours so when more time then there may be chance of Memory Leaks issue. 

• Spike Testing: Spike Testing is the testing in which suddenly Test Team increase/decrease the load over the system by a varying number of users and then observing the behavior of the system. The Objective of this sudden increase of load to check weather performance will suffer, system get crash or it handled this sudden increase/decrease load.

• Volume Testing: In this type of Testing, We put the huge load for the limited time to check the behavior of the Application. Suppose you want the Volume Test then you need to increase the size of the database so that it can accept the heavy load so in this testing we check the performance of database with increasing volume.

• Scalability Testing: Scalability Testing is the non functional Testing. In this Testing we check the capability of the system in scale up or scale down. Scale Up and Scale down to means to check the capability of the system or Network to check the growing amount of work in order to accommodate that growth. In Scalability Testing we measure the system capability in terms of growing the workload per user, Growing the concurrent users or the size of the database.

• Configuration Testing: Configuration Testing is the testing type in which test team test the software with every combination of the supported Software and the hardware.  In configuration testing we define with the software guideline of supported version (Software and Hardware) in which software will work. We run all test cases with these combination to verify the result.

• Isolation Testing: In the Isolation Testing, Test team break the system in the different modules so that bug can be easily visible in the software.  We use Isolation Testing where bug is not spotted easily.