I did see some of the earliest posts regarding this topic. But I am looking for something different.
In SilkTest if Verify function failed, the control will go to testcase exit function by terminating script. Adding do...except is one way of doing this.
I want to know, whether there is any other way handling this commonly in testcase exit function or writing a common error handling function which can be called automatically whenever an exception occurs and continue the execution of rest of the script.
Thanks for the help,
I got solution in different way.
I wrote my own Verify Function and replaced Verify Calls with vVerifyData ..as follows:
[-] void vVerifyData(ANYTYPE aActualData,ANYTYPE aExpectedValue,ANYTYPE aTitle optional)
I solve the problem the same way, by writing special versions of Verify().
One nice trick to learn is that when a Verify() error is logged in the results, you can highlight the error and select "Results -> Update Expected Value" to automatically copy/paste the data into your test.
This trick does not work unless you add "hidecalls" to your special Verify().
A bug in SilkTest also requires that you either eliminate the optional "Description" parameter, or move it and make it required.
Run this code to generate an error, then select "Results -> Update Expected Value" to see what I mean: