A compound recovery scenario defines a crash or exception event and the operation(s) required to continue or restart the test and the associated applications. You define and modify compound recovery scenarios from the Compound tab of the Recovery Manager. The Recovery wizard guides you through the process of creating and modifying your scenario.
To create a compound recovery scenario
For example, suppose that your application uses a green button to indicate that an electrical network is closed; the same button may turn red when the network is broken. Your test cannot continue while the network is broken.
For example, suppose part of your test includes clicking on a Print button to send a generated graph to the printer, and a message box opens indicating that the printer is out of paper. Your test cannot continue until you close the message box.
Click Next.
Enter a name containing only alphanumeric characters and underscores (no spaces or special characters) and a description for your recovery scenario.
Click Next.
If you chose a crash event in step 4, there is no need to define the event.
Proceed to step 7
If you chose an object event in step 4, enter the following information:
If you want to define a window as the exception object, click on the window’s title bar, or enter the window’s logical name and leave the Object name box empty.
Click Next and proceed to step 7
If you chose a pop-up event in step 4, enter the following information:
If the window is not already saved in the GUI Map and you use the pointing hand to identify the window, WinRunner automatically adds it to the active GUI Map. If the window is not already saved in the GUI Map and you type the name manually, WinRunner identifies the pop-up exception when a pop-up window opens with a title bar matching the name you entered.
Click Next and proceed to step 7
If you chose a TSL event in step 4, enter the following information:
Click Next.
The Define Recovery Operations screen opens and displays the recovery operations WinRunner can perform when the exception occurs. Note that WinRunner performs the recovery operations you select according to the order displayed in the dialog box. Select any of the following options:
If you select Reboot the computer, consider the following:
Click Next.
If you selected Close processes, proceed to step 8.
If you did not select Close processes or Reboot the computer, proceed to step 9.
If you selected Reboot the computer, but not Close processes, proceed to step 10.
Specify the application processes that you want WinRunner to close when the exception event occurs. When WinRunner runs the recovery scenario, it ignores listed application processes that are already closed (no error occurs).
To add an application to the list, double-click the next blank space on the list and type or browse to enter the application name, or click Select Process to open the Processes list. The Processes list contains a list of processes that are currently running.
To add a process from this list to the Close Application Processes list, select the process and click OK.
Click Next. If you selected Reboot the computer in the previous step, proceed to step 10. Otherwise, proceed to step 9.
Choose from the following options:
The post-recovery function can be useful for reopening applications that were closed during the recovery process and/or setting applications to the desired state.
Click Next.
Click Finish. The recovery scenario is added to the Compound tab of the Recovery Manager dialog box. If you selected Activate by default (and any required objects are found in the loaded GUI map file(s)), the recovery scenario is activated. Otherwise the recovery scenario remains inactive.
Defining Recovery Scenario Functions
You can define recovery functions that instruct WinRunner to respond to an exception event in a way that meets your specific testing needs. You can also define post-recovery functions for compound recovery scenarios. These functions can be useful to re-open applications that may have closed when the exception occurred or during the recovery process, and to set applications to the desired state.
You use the Recovery Function or Post-Recovery Function dialog box that opens from the Recovery wizard to define new recovery and post-recovery functions. The dialog box displays the syntax and a function prototype for the selected exception type.
Once you have defined a recovery function, you can save it in the recovery compiled module, paste it into the current test, or copy it to the clipboard.
To define a recovery or post-recovery function:
|
|
WinRunner Related Tutorials |
|
---|---|
LoadRunner Tutorial | HTML Tutorial |
QTP Tutorial |
WinRunner Related Interview Questions |
|
---|---|
SILK TEST Interview Questions | LoadRunner Interview Questions |
WinRunner Interview Questions | HTML Interview Questions |
QTP Interview Questions | Manual Testing Interview Questions |
OpenStack Interview Questions | Automation Testing Interview Questions |
API testing Interview Questions | Rational robot Interview Questions |
Selenium IDE Interview Questions | Performance Testing Interview Questions |
Test Director Interview Questions |
Winrunner Tutorial
Introduction
Winrunner At A Glance
Understanding How Winrunner Identifies Gui Objects
Understanding Basic Gui Map Concepts
Working In The Global Gui Map File Mode
Editing The Gui Map
Merging Gui Map Files
Configuring The Gui Map
Learning Virtual Objects
Designing Tests
Checking Gui Objects
Working In The Gui Map File Per Test Mode
Working With Web Objects
Working With Activex And Visual Basic Controls
Checking Powerbuilder Applications
Checking Table Contents
Checking Databases
Checking Bitmaps
Checking Text
Checking Dates
Creating Data-driven Tests
Synchronizing The Test Run
Defining And Using Recovery Scenarios
Handling Web Exceptions
Using Regular Expressions
Enhancing Your Test Scripts With Programming
Generating Functions
Calling Tests
Creating User-defined Functions
Creating Compiled Modules
Calling Functions From External Libraries
Creating Dialog Boxes For Interactive Input
Understanding Test Runs
Analyzing Test Results
Running Batch Tests
Running Tests From The Command Line
Controlling Your Test Run
Using Breakpoints
Monitoring Variables
Setting Properties For A Single Test
Setting Global Testing Options
Customizing The Test Script Editor
Customizing The Winrunner User Interface
Setting Testing Options From A Test Script
Customizing The Function Generator
Initializing Special Configurations
Integrating With Quicktest Professional
Managing The Testing Process
Testing Systems Under Load
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.