RECOVERY TESTING

Recovery testing is basically done in order to check how fast and better the application can recover against any type of crash or hardware failure etc. Type or extent of recovery is specified in the requirement specifications. It is basically testing how well a system recovers from crashes, hardware failures, or other catastrophic problems

In software testing, recovery testing is the activity of testing how well the application is able to recover from crashes, hardware failures and other similar problems.

Recovery testing is the forced failure of the software in a variety of ways to verify that recovery is properly performed. Recovery testing should not be confused with reliability testing, which is tries to discover the point at which failure occurs.

Examples of recovery testing:

   1. While the application running, suddenly restart the computer and after that check the validness of application's data integrity;
   2. While application receives data from the network, unplug and then in some time plug-in the cable, and analyze the application ability to continue receiving of data from that point, when network connection disappeared;
   3. To restart the system while the browser will have definite number of sessions and after rebooting check, that it is able to recover all of them.

■	Load Testing
■	Stress Testing
■	Domain Testing
■	Exploratory Testing
■	Recovery Testing
■	User Acceptance Testing
■	Alpha Testing
■	Beta Testing
■	Unit Testing
■	Static & Dynamic Analysis Testing
■	Functional Testing
■	Ad-hoc Testing
■	Volume Testing

Related Links :

Recovery Testing