| || |
Driver script errors
I wonder if anyone can help with the following, I have looked in the search, but can't see a solution.
I am using a driver script to call other scripts in my test process.
If one of the sub scripts fails, I only get the line in the driver script displayed in debug, it is not possible (as far as I can see) to see which line in the sub script is causing the problem.
This means that when using the driver script, I am unable to log, or trace the issue.
Is there a variable that holds the actual location of the current step in the script? Or is there another way of doing this?
I know that many others use driver scripts and so feel sure someone will know how to help, or at least what the common solution is.
Re: Driver script errors
I have met this problem. The debugger has sometimes problems with opening the right subscript where the error occurred. Open it for him before running the driver script. Sometimes even this is not enough: put then a breakpoint in the driver script where it calls the subscript, debug inside and run. Sometimes, after a big amount of debugging, script corrections etc the debugger is so tired that it is better to close TestPartner and start again.
While running automatic tests:
Make sure each script has its own error handler. The object Error has information about the line number where the error occurred (only for TestPartner errors like failed attach, but not for BV errors like division by zero).