Another type of performance testing is scalability testing, which comes under the under non functional testing of software testing
It is used to check an application’s performance by increasing or decreasing the load in particular scales known as scalability testing. It is executed at a hardware, software, or database level.
It is specified as the capacity of a network, system, application, product, or process to make the function correctly when modifications are made in the system’s size or volume to meet an increasing need.
In this testing, the Test cases are designed and implemented in a well-organized manner. It also analysis the system, processes, or database’s ability to meet an upward need.
Following are the critical purposes of scalability testing:
The Objective of Scalability Testing
- The main objective of performing the scalability testing is to control how the application balances with an increasing workload and at what point the software product or the system stops scaling and identify the reason behind it.
- The scalability testing is needed to signify the user limit for the software product.
- To find out the client-side degradation, end-user involvement under load, and server-side stability.
- The usages of scalability testing will make sure the ability of software to scale up with the increasing workload and data traffic.
Types of Scalability testing
Scalability testing is classified into two parts, which are as follows:
- Upward scalability testing
- Downward scalability testing
Upward scalability testing
The upward scalability testing is used to expand the number of users on a specific scale until we got a crash point. It is mainly used to identify the maximum capacity of an application.
Downward scalability testing
Another type of scalability testing is downward scalability testing. When the load testing is not passed, we will use the downward scalability testing and then start decreasing the number of users in a particular interval until the goal is achieved.
Therefore, we can quickly identify the bottleneck (bug) by performing downward scalability testing.