Micro Focus QTP (UFT) Forums
Add new recovery scenario to existing tests - Printable Version

+- Micro Focus QTP (UFT) Forums (https://www.learnqtp.com/forums)
+-- Forum: Micro Focus UFT (earlier known as QTP) (https://www.learnqtp.com/forums/Forum-Micro-Focus-UFT-earlier-known-as-QTP)
+--- Forum: UFT / QTP Others (https://www.learnqtp.com/forums/Forum-UFT-QTP-Others)
+--- Thread: Add new recovery scenario to existing tests (/Thread-Add-new-recovery-scenario-to-existing-tests)



Add new recovery scenario to existing tests - Autobot - 08-11-2015

Hi, is there a way to easily add a new Recovery Scenario to all existing tests? Other than opening each one and adding it? The recovery scenario is stored on ALM.

Thanks


RE: Add new recovery scenario to existing tests - QTP.learning - 08-14-2015

Hi Autobot ,
I think you are asking AUT error handling. . If you want to handle errors in as given AUT then you can write some function call this function for each step .
=================example =====
Code:
function(object)
If object.Exist Then
   function = "pass"
Else
  Reporter.ReportEvent micFail,object  &" Not Found"
    function = "fail"
End if

But Exception handing cant be generic it should handle specific scenarios in specfic screen.

Let me know whether my answer cleared your doubts.

Thanks
Bharadwaj


RE: Add new recovery scenario to existing tests - ravi.gajul - 08-15-2015

Select the check box "Add scenario to default test settings" in the last step of recovery scenario wizard. This will make it available with every script that you open.


RE: Add new recovery scenario to existing tests - workrohit08 - 03-08-2017

(08-15-2015, 11:42 PM)ravi.gajul Wrote: Select the check box "Add scenario to default test settings" in the last step of recovery scenario wizard. This will make it available with every script that you open.

Will this recovery scenario be available to other scripts on a different machine. I run my automation suite on 2 machines.

I am using ALM 11 to run scripts directly from each individual machine, instead of triggering them remotely.