Forum Discussion
Hi,
> Is there a way to bypass or make the "Stop on Error" property ignore these scenarios?
I am not aware about such option.
You may consider opposite approach - do not stop test on error but use Runner.Stop() / Runner.Halt() methods to stop test when really needed.
- TCYKPB3 years agoContributor
I have considered that, but I still want to stop on errors when, for example, a Click() in an object fails, or a Checkpoint fails. I just want to avoid the Stop when the TestedApp fails to Run() (or find a workaround to make it open 100% of the times without errors).
- brumazz3 years agoSmartBear Alumni (Retired)
This might be a bit basic, but what about just adding an If..Then statement to look for the needed process to be running.... and if not then launch it.
- TCYKPB3 years agoContributor
Hi brumazz , my code looks something like this:
if not (Sys.WaitProcess("myapp.exe").Exists) {
TestedApps.MyApp.Run() // <--- Here Test Complete throws an error 4/10 times, and the execution is stopped even if I put it inside a try/catch
}
The problem here is how TestComplete manages the errors with the "Stop On Error" option selected (or, to be more specific, the fact that TestComplete throws errors on simple actions as opening an application). It would be great if there is a way to ignore these type of errors, because I could simply manage them by "retrying" one more time the same action until succeeds.
Related Content
Recent Discussions
- 5 hours agojstaehlin
- 23 hours agoAivanitskiy