In the last topic, we learned about Performance Testing. And in this topic, we will learn about Recovery Testing.Now, We will move ahead with Recovery Testing’s Introduction, example and will see why it is used. Let's see the Introduction. Recovery Testing is a type of non-functional testing in which we will test that if the system crashes in any circumstance then How quickly will it get back? In Recovery Testing, we forcefully crash any system and then see how quickly the system is recovering on its own. Recovery Testing can be done at the time of Performance Testing. We have taken an example here. When an application is receiving data from the network. What we will do is we will unplug the plug; we will remove the plug and then after sometime we fix the plug again and then we will see if our application starts to receive the data or not. If it is starting, is it starting from where it was broken or from the beginning. You must have seen it most of the time at the time of downloading. you can relate, right? Do you remember, sometimes it goes to 98% and then gets stopped. Then what happens, if the application is good, it will not start from 1. It will start from 99. But if the application crashes, it will start from 1. What is the need for Recovery Testing? Recovery Testing is performed by a trained tester and that too very accurately for an extent. What happens because of that is the risk of failure is reduced in the market. Recovery Testing is necessary to ensure that all backups are successfully taken at a particular interval. Back up of what? Client database, Server database, etc. where our data is there which we are using daily, that backup should be taken at a particular time interval. We learned about Recovery Testing, we saw an example and we also saw the need for Recovery Testing. In the next topic, we will see Compatibility Testing.
Share a personalized message with your friends.