QTP基础教程-Recovery Scenarios.pptVIP

Recovery Scenarios Objectives After completing this chapter, you will be able to: Define a test exception. Create a recovery scenario. Associate a recovery scenario with a test. Exceptional Events Unexpected or unpredicted events that occur during a test run that may cause invalid test results or suspension of the test run before completion. - An exception can occur in the AUT or can come from an external source. For example, the window “You have mail” or “Printer Out Of Paper” or notification of secure and non-secure messages due to different setups on browsers. - Examples of errors that are not exceptions: an expected error message window when a bad password is entered, a prompt to save changes, a prompt to fill in an empty edit field. Recovery Scenario The Recovery Scenario Manager allows the tester to create and manage recovery scenarios to identify and take appropriate action when an exception occurs. Use a recovery scenario for exceptional or unpredictable events. Handle expected errors and predictable events directly in the test. Recovery Manager Figure 1 Recovery Manager Wizard Recovery Manager To access the Recovery Manager, choose TOOLS?RECOVERY SCENARIO MANAGER. Identify the trigger. Define the recovery operation. Define the post recovery operation. Associate the recovery scenario with a test. Recovery Wizard Steps Recovery Wizard These are the steps to create a new recovery scenario file as opposed to adding an existing recovery scenario to a test: Click on the NEW ORDER icon. Identify the potential error. Set a trigger to detect whether the error has occurred. Take pre-determined steps to recover from the error. Set post-recovery steps. Recovery Wizard Steps The Event Trigger Figure 3 trigger Event-Pop-Up The first component of the recovery process is to identify the event that interrupts your test run. Examples: - A pop-up window - An unacceptable object state - A test step that did not complete successfully - An application crash The Event