Stability Testing is a type of Software Testing to check the quality and behavior of the software in different environmental parameters. It is defined as the ability of the product to continue to function over time without failure.
It is a Non-functional Testing technique that focuses to stress the software component to the maximum. Stability testing is done to check the efficiency of a developed product beyond normal operational capacity that is known as break point. It has higher significance in error handling, software reliability, robustness and scalability of a product under heavy load rather than checking the system behavior under normal circumstances.
Stability testing assesses stability problems. This testing is majorly intended to check whether the application will crash at any point in time or not.
Objective of the Stability Testing:
The objective of the stability testing is:
- To yield confidence in the stability of the system or software application under test.
- To ensure the system handling big programs.
- To operate the effectiveness of the system or software application.
- To check the stability of the system under stress.
Stability Testing Process:
Effects of not performing Stability Testing:
- If stability testing is not carried out, system slows down with large amount of data.
- Without stability testing, system crashes suddenly.
- In absence of stability testing, System’s behavior is abnormal when it goes to different environment.
- In absence of stability testing, system’s performance decreases which in turn can have bad effects on the business.
Testing Tools used in Stability Testing:
1. Apache JMeter 2. NeoLoad 3. WebLOAD 4. LoadRunner
Advantages of Stability Testing:
- It gives the limit of the data that a system can handle practically.
- It provides the confidence on the performance of the system.
- It determines the stability and robustness of the system under load.
- Stability testing leads to a better end user experience.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Beta Testing | Software Testing
- Software Engineering | Differences between Sanity Testing and Smoke Testing
- Software Testing | Endurance Testing
- Software Testing | Dynamic Testing
- Software Testing | Accessibility Testing
- Smoke Testing | Software Testing
- Performance Testing | Software Testing
- Software Testing | Non-functional Testing
- Sandwich Testing | Software Testing
- Software Engineering | Comparison between Regression Testing and Re-Testing
- Alpha Testing | Software Testing
- Unit Testing | Software Testing
- Stress Testing | Software Testing
- Sanity Testing | Software Testing
- Gray Box Testing | Software Testing
- Acceptance Testing | Software Testing
- Software Testing | Reliability Testing
- Software Testing | Scalability Testing
- Software Testing | Manual Testing
- Software Testing | Scenario Testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.