Recovery is the ability to restart operations after the integrity of the application has been lost. The process normally involves reverting to a point where the integrity of the system is known, and then reprocessing transactions up until the point of failure.
The time required to recover operations is affected by the number of restart points, the volume of applications run on the computer center, the training and skill of the people conducting the recovery operation, and the tools available for recovery. The importance of recovery will vary from application to application.
Objectives :
Recovery testing is used to ensure that operations can be continued after a disaster. Recovery testing not only verifies the recovery process, but also the effectiveness of the component parts of that process. Specific objectives of recovery testing include:
Recovery testing can be conducted in two modes. First, the procedures, methods, tools, and techniques can be assessed to evaluate whether they appear adequate; and second, after the system has been developed, a failure can be introduced into the system and the ability to recover tested. Both types of recovery testing are important. The implementation of the technique is different depending upon which type of recovery testing is being performed.
Evaluating the procedures and documentation is a process using primarily judgment and checklists. On the other hand, the actual recovery test may involve off-site facilities and alternate processing locations.
Testing the procedures is normally done by skilled systems analysts, professional testers, or management personnel. On the other hand, testing the actual recovery procedures should be performed by computer operators and other clerical personnel, who would be involved had there been an actual disaster instead of a test disaster.
A simulated disaster is usually performed on one aspect of the application system. For example, the test may be designed to determine whether people using the system can continue processing and recover computer operations after computer operations cease.
While several aspects of recovery need to be tested, it is better to test one segment at a time rather than induce multiple failures at a single time. When multiple failures are induced, and problems are encountered, it may be more difficult to pinpoint the cause of the problem than when only a single failure is induced.
When to Use Recovery Testing ?
Recovery testing should be performed whenever the user of the application states that the continuity of operation of the application is essential to the proper functioning of the user area. The user should estimate the potential loss associated with inability to recover operations over various time spans; for example, the inability to recover within five minutes, one hour, eight hours, and a week. The amount of the potential loss should both determine the amount of resource to be put into disaster planning as well as recovery testing.(128.4)
CONDITION TESTING
TESTING CONDITIONS PART ONE
TESTING CONDITIONS PART TWO
TESTING CONDITIONS PART THREE
TESTING CONDITIONS PART FOUR
SPECIFIC FIELD TESTING
USABILITY TESTING
INTEGRATION TESTING
INTEGRATION TESTING PART ONE
INTEGRATION TESTING PART TWO
INTEGRATION TESTING PART THREE
INTEGRATION TESTING PART FOUR
INTEGRATION TESTING PART FIVE
INTEGRATION TEST STANDARDS
INTEGRATION TEST STANDARDS PART TWO
The time required to recover operations is affected by the number of restart points, the volume of applications run on the computer center, the training and skill of the people conducting the recovery operation, and the tools available for recovery. The importance of recovery will vary from application to application.
Objectives :
Recovery testing is used to ensure that operations can be continued after a disaster. Recovery testing not only verifies the recovery process, but also the effectiveness of the component parts of that process. Specific objectives of recovery testing include:
- Preserve adequate backup data
- Store backup data in a secure location
- Document recovery procedures
- Assign and train recovery personnel
- Develop recovery tools and make available
Recovery testing can be conducted in two modes. First, the procedures, methods, tools, and techniques can be assessed to evaluate whether they appear adequate; and second, after the system has been developed, a failure can be introduced into the system and the ability to recover tested. Both types of recovery testing are important. The implementation of the technique is different depending upon which type of recovery testing is being performed.
Evaluating the procedures and documentation is a process using primarily judgment and checklists. On the other hand, the actual recovery test may involve off-site facilities and alternate processing locations.
Testing the procedures is normally done by skilled systems analysts, professional testers, or management personnel. On the other hand, testing the actual recovery procedures should be performed by computer operators and other clerical personnel, who would be involved had there been an actual disaster instead of a test disaster.
A simulated disaster is usually performed on one aspect of the application system. For example, the test may be designed to determine whether people using the system can continue processing and recover computer operations after computer operations cease.
While several aspects of recovery need to be tested, it is better to test one segment at a time rather than induce multiple failures at a single time. When multiple failures are induced, and problems are encountered, it may be more difficult to pinpoint the cause of the problem than when only a single failure is induced.
When to Use Recovery Testing ?
Recovery testing should be performed whenever the user of the application states that the continuity of operation of the application is essential to the proper functioning of the user area. The user should estimate the potential loss associated with inability to recover operations over various time spans; for example, the inability to recover within five minutes, one hour, eight hours, and a week. The amount of the potential loss should both determine the amount of resource to be put into disaster planning as well as recovery testing.(128.4)
CONDITION TESTING
TESTING CONDITIONS PART ONE
TESTING CONDITIONS PART TWO
TESTING CONDITIONS PART THREE
TESTING CONDITIONS PART FOUR
SPECIFIC FIELD TESTING
USABILITY TESTING
INTEGRATION TESTING
INTEGRATION TESTING PART ONE
INTEGRATION TESTING PART TWO
INTEGRATION TESTING PART THREE
INTEGRATION TESTING PART FOUR
INTEGRATION TESTING PART FIVE
INTEGRATION TEST STANDARDS
INTEGRATION TEST STANDARDS PART TWO
No comments:
Post a Comment