Re: Making scripts more robust like exception handling and error recovery?
If you are using WinRunner 7.01 then go to the Mercury Support website and try the patch "wr701p107 - tsl exception & web addin set_window fail".
Follow the instructions that come with the patch. If you receive an error when you run WinRunner there is a missing folder in the "ns_lib" folder. So create an empty folder called "exp" and put it in the "ns_lib" folder then run WinRunner.
This will help fix some of the problems.
If you do not know where the patch is, go to support.merc-int.com, then Downloads, Download Patches, WR 7.01, WebTest and it is under there.
Making scripts more robust like exception handling and error recovery?
User rickhunter2002us (email@example.com) posted:
Can anyone point to online tutorials or share ideas to make WinRunner
web scripts more robust? Questions include the following.
1) Exception handling. For Tools > Web Exception Handling - Do you
check all exceptions listed? What are some you add to the list? How
do you handle timeouts for set_window for example? What if the
browser is hanging, do you click on the STOP button in IE 5.5 for
example, or is the best way to quit browser, remember where you are
then do the test over again? If so how do you track tests completed
so far, a global variable?
2) TSL Exceptions. How to use these to handle common error codes
like a webpage timeout or failed test?
3) Recovery from errors. Using WinRunner only (no Test Director) how
do you recover from errors? If you have a failure and it jumps to an
exception function you created in TSL, how do you know where the
Thank you in advancd for any tutorials or ideas in these areas. Seem
like these are common problems, so I am hoping there is some
discussion material already out there.