| || |
We all know that QTP's Recovery Scenario feature is not 100% reliable and moreover adding a lot of recovery scenarios in a test slows down the execution as well. I was wondering if it is possible to completely do away with the recovery scenarios.
I read an article in www.advancedqtp.com where the author is talking about the RegisteredUserFunc -
one benefit of QTP's RS is that it can handle the popup or errors at any point in the application.
With RegisterUserFunc method user should know that exactly at which step in the application he will get the exception popup and have to perform the close operation to call the RegisteredUserFunction.
Please let me know if anyone has used this method instead of the painful recovery scenarios in their automation framework