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.

How does QTP identify an object?

0 Answers  

---

I am new to automation testing.I am learning QTP 9.2.my question is how to install the defferent addins(other than Default Addins) is there any defference in QTP after installing the Addins.where we can get the addins?

0 Answers  

---

tell me exact differenceb bw qtp and selenium?(could not tell open soure and licennce? difference in usage and technical difference?

0 Answers  

---

using descriptive programming how to close all opend browsers?

7 Answers   Satyam,

---

How many types of Check Point in QTP

2 Answers   R Systems,

---

why use Description programming? what is advantages and disadvantage of this methods?

2 Answers  

---

What is the function of Filter in QC . give with a real time example.

1 Answers   TCS,

---

Where to use Property Let, Property Get, Property Set in UFT

0 Answers  

---

how you update scripts in qtp?

1 Answers  

---

Hi guys, Our company has started to automate testing and started using the tool QTP.Iam new to QTP and I have the following questions to ask. Would appreciate if anyone could give me a hand on this and explain things in a detailed way. [1] Bugs outside checkpoints: I know that I can easily make the QTP do what I want inside the application. Also, I know that I can insert some checkpoints and that the qtp will notice if those conditions are not met. However, there are bugs and problems that might not be connected to a checkpoint (system crash, database error, losing session/logout etc.); how can I make sure that the QTP will notice such problems as well and flag a test as failed. [2] How to tell the QTP that when a particular statement is "false",it should flag it as, test failed and show in in the test report. In short how to tell the qtp that a test is false from the script so that it shows it in the report For Eg:- if(true) test passed // how to instruct qtp else test failed // how to instruct qtp [3] Test script portability: we are having several environments; If I record a test on User Interface, obviously, the qtp will save the URL; however, how can I make the qtp run the tests so that the url is provided dynamically. Is there a possibility to parameterize the web server.Is this the way to do it.I dont know? [4] Test management: How do I manage the tests? I guess we will be doing it in Quality Center, yet, it’s not perfectly clear to me how we will be doing that. [5] Running scheduled test sets: How do I group tests to a certain test set? How can I make this test set run at a predefined time? [6] Test maintenance: What do we need to do beforehand in order to enable for easy test maintenance, meaning small adjustments in tests? [7] Reports: What kind of reports on test results are available (either QTP or Quality Center)? Thanks in advance and hoping for an answer. Jen

0 Answers  

---

can any one tell me the script to click on a button in the wintoolbar.

1 Answers  

---

• Re –Engineering the regression testing from 0% to 60% automation. This has saved 4-mandays in every release. what doeas this statement means

2 Answers   Infosys,

---