Failover Testing, Recovery Testing, Security Testing

Failover Testing

Failover testing is a testing technique that validates a system’s ability to be able to allocate extra resources and to move operations to back-up systems during the server failure due to one or the other reasons. This determines if a system is capable of handling extra resources such as additional CPU or servers during critical failures or at the point the system reaches a performance threshold.

Failover testing is very much critical for the following types of applications:

• Banking Application
• Financial Application
• Telecom Application
• Trading Platforms

Recovery Testing

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

Recovery testing is done in order to check how fast and better the application can recover after it has gone through any type of crash or hardware failure etc. Recovery testing is the forced failure of the software in a variety of ways to verify that recovery is properly performed. For example, when an application is receiving data from a network. unplug the connecting cable. After some time, plug the cable back in and analyze the application’s ability to continue receiving data from the point at which the network connection got disappeared. Restart the system while a browser has a definite number of sessions and check whether the browser is able to recover all of them or not.

Security Testing

Security testing is basically to check whether the application or the product is secured or not. Can anyone come tomorrow and hack the system or login the application without any authorization. It is a process to determine that an information system protects data and maintains functionality as intended.