Forum Discussion
Hi Sergeys
Have you tried just the Runner.Pause and if not Runner.stop without the exceptions, login failed etc. prior to stopping the test? Want to eliminate other aspects of the function
Regards
Damien Walsh
Technical Sales Engineer
Checking the content of error message is implemented by design - anyway I don't think that simplifying function to be just if (...) Runner.Pause else Runner.Stop will solve the problem, as after pause work - it jumps to the last '}' line of function. And afterwards - when clicking on Stop manually - it crashes.
I've just implemented workaround - by replacing 'Runner.Pause' by 'Log.Message(...)' and setting breakpoint for it - thus no crashes and it works the same way as I expected.
- sergeys8 years agoContributor
Actually it is failing as well with exception, so the question is still actual...