Answer / kavitha

Generally we go for this recovery scenario manager to
handle known errors which are occurred in un known places at
runtime we can use this.

we have four events in this recovery scenario manger
advantages of this,

application crash- to handle crashed applications at runtime
we can use this event

pop-up window- to handle unwanted windows of application
build at runtime we can use this event

test run error-to handle vb script statement errors at
runtime we can use this event

object state-to handle object related errors at runtime we
can use this event

Answer / kondalrao

output result in not failed but temparory output as (Not
success) with warning then it is known as recoveryscenario
qtp as the tools and select recovery scenario as 4 types
1.pop up window
2.object state
3.error handling
4.

for eg:flightreservation
login and password with recording close the
application(result will be passed)
script:window("login").activate
window("login").window("password").set"kondalrao"
window("login").winbutton("ok").click
in this last statement used in name after
result will be failed(please enter password)
go to tools and select recovery scenario as first pop
widow used in this application to click on next button
add keyboard and mouse operation and select the hand icon
means to select (enter the password) add the object as not
click(click the add object not the next button this not
selected)next click on finished and saved the file finally
result(not failed and not passed ) temperory execution with
warning

Answer / jaspreet kaur vohra

Unexpected events, errors, and application crashes during a run session can disrupt your run session and distort results. This is a problem particularly when tests run unattended—the test pauses until you perform the operation needed to recover. To handle situations such as these, QuickTest enables you to create recovery scenarios and associate them with specific tests. Recovery scenarios activate specific recovery operations when trigger events occur. For information on when to use recovery scenarios, see Deciding When to Use Recovery Scenarios.

The Recovery Scenario Manager provides a wizard that guides you through the process of defining a recovery scenario, which includes a definition of an unexpected event and the operations necessary to recover the run session. For example, you can instruct QuickTest to detect a Printer out of paper message and recover the run session by clicking the OK button to close the message and continue the test.

A recovery scenario consists of the following:

Trigger Event. The event that interrupts your run session. For example, a window that may pop up on screen, or a QuickTest run error.
Recovery Operations. The operations to perform to enable QuickTest to continue running the test after the trigger event interrupts the run session. For example, clicking an OK button in a pop-up window, or restarting Microsoft Windows.
Post-Recovery Test Run Option. The instructions on how QuickTest should proceed after the recovery operations have been performed, and from which point in the test QuickTest should continue, if at all. For example, you may want to restart a test from the beginning, or skip a step entirely and continue with the next step in the test.
Recovery scenarios are saved in recovery scenario files. A recovery scenario file is a logical collection of recovery scenarios, grouped according to your own specific requirements.

To instruct QuickTest to perform a recovery scenario during a run session, you must first associate the recovery scenario with that test. A test can have any number of recovery scenarios associated with it. You can prioritize the scenarios associated with your test to ensure that trigger events are recognized and handled in the required order. For more information, see Adding Recovery Scenarios to Your Test.

When you run a test for which you have defined recovery scenarios and an error occurs, QuickTest looks for the defined trigger events that caused the error. If a trigger event has occurred, QuickTest performs the corresponding recovery and post-recovery operations.

You can also control and activate your recovery scenarios during the run session by inserting Recovery statements into your test. For more information, see Programmatically Controlling the Recovery Mechanism.

Note: If you select On error in the Activate recovery scenarios box in the Recovery pane of the Test Settings dialog box, the recovery mechanism does not handle triggers that occur in the last step of a test. If you chose this option and need to recover from an unexpected event or error that may occur in the last step of a test, you can do this by adding an extra step to the end of your test.

For Regression testing already written test cases are sufficient?

2 Answers   CTS,

---

Explain the QTP Tool interface.

2 Answers   Crea,

---

what is the difference between wait and wait function

1 Answers   TCS, Wipro,

---

how to post xml data from QTP scripts to any application?

0 Answers  

---

How you debug your script?

0 Answers  

---

I recorded a Web based Application running on JAVA and when I went to play them back a week later they didn't run. I noticed that the Browser was putting in a (Underscore and a Number) for each line so i re-recorded and noticed the Underscore line wasn't the same as what i recorded last week so any script I record today will not work next week because the browser settings or how QTP recognizes it keeps changing. This is the new line Browser("Bureau of Labor Statistics_4").Page("Bureau of Labor Statistics").JavaApplet("SurveyApplet").JavaList ("Select an Area").Select "U.S. city average" This is the old line 'Browser("Bureau of Labor Statistics_3").Page("Bureau of Labor Statistics").JavaApplet("SurveyApplet").JavaList ("Select an Area").Select "U.S. city average" Notice the Burearu of Labor Statistics_3 adn Burearu of Labor Statistics_4. Why does it change and how do I prevent it from changing.

5 Answers  

---

when we right click on the desktop of any operating system we find a menu , consisting of refresh,edit,open,paste and cut etc... how to load the object and object properties of that menu in QTP

3 Answers   iFlex,

---

QTP 1.What type of bugs u commonly find in u r project? 2.what is agile testing explain with example? 3.application is given req n functionality r missing then how can u start testing? 4.what r the types of defect tracking tools? 5.what is functionality testing? 6.what is change req how u use it? 7.diff bet gul n functional testing? 8.test cases for IE 6.0? 9.where do u store test cases? 10.what r design objects in qtp? 11.what r 5 types of objects in qtp? 12.how to change .mtr to .tsr n vice versa? 13.in which situations qtp will not recoznize objects? 14.how to call .vbs fuctions, library files in qtp? 15.if 10 windows r ope write command to close all windows in qtp? 16from what stage u start automation in u r project? 17.what is VSS? it is usedin automationr manual? 18.size of object repository? 19.how to conduct GUI testing n performance testing on MS-Word? what r performance TEST CASES? 20. use of virtual objects explain? 21.how to connect buzilla with qtp? 22. what is API ? 23.how to merge 2 object repositories in qtp? 24.what is recovery scenario manager? 25. diff bet link n hyper link? 26.diff bet test case n test case scenario? 27.what is relational testing? 28.where do we write test cases? 29.what is base line in testing? 30.what r key process areas(KPA) in u r company? 31.what is hot fix? 32.what is sql injection? 33.what is valnerability? 34.what is TOM in qtp? 35.can we do qtp testing with out creating objects in object repository? can we completely write code in expert view only? 36.where we cant do automation testig? give example using OR is a advantage r a disadvantage?

6 Answers   IBM,

---

What are FAST and NORMAL modes in qtp ? Why r these modes intended for ?

3 Answers   IBM,

---

how to get no.of non empty rows in a excel sheet through vb-script

2 Answers   HP,

---

Error handling

3 Answers   Wipro,

---

WHat is Object Identification and Object Spy?

2 Answers   IBM,

---