![]() The fact that it says "ask whether." implies to me that it should somehow be possible to debug in these cases. If this is unchecked and I run the example above it just stops execution without throwing the runtime exception popup. Use the compressed production version to simply fix compatibility issues without generating console warnings. ![]() In the project properties, on the Playback section, there is the "Error Dialog" checkbox. Microsoft Script Debugger is relatively minimal debugger for Windows Script Host-supported scripting languages, such as VBScript and JScript. However, this is not always a viable option because in our systems there is a lot of non-user-entered data that effects our test cases that changes from run to run (stock prices, etc), so there's no guarantee the error will happen again on the next rerun. It will take you to UFT One Downloads page. I realize you can stop the test run, put a breakpoint on a line right before where the error occurred, and run to the breakpoint on a 2nd execution. I need to know if there's any way to get TestComplete to allow you to debug from the current line that threw the error so you can figure out exactly why it had the error. However, this popup only has an OK button, which when clicked completely stops the script execution. If I run this, it gives a VBScript runtime error popup. managing, maintaining, coordinating and executing the test scripts for complex. The easiest way of replicating what I mean is to write a few lines of code that forces a divide by 0: Software Quality Assurance Specialist - Automation Testing - QTP. ![]() I was wondering if anyone could give me a definitive answer as to whether or not it SHOULD be possible to debug a script after a runtime error.
0 Comments
Leave a Reply. |