Developing vbs test scripts, I often get Errors not visible during compile time, as vbs is not type safe.
What I need is – in case of a vbs runtime error or a TC error – an option to keep the test run alive and debug it, like TC“Pause test execution” option.
“Pause test execution” would be perfect, if it would stop the test run AFTER processing the OnLogError event, but BEFORE actually printing the error message.
This would give me a chance to set LogParams.Locked = True in the event handler and suppress the error without unwantedly stopping the test run.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.