How to avoid certain "Stop on Error" scenarios?

Question

Hello, I have my project configured to Stop on Errors when I run my test cases, but there are some errors which are not functional bugs (very frequently the TestedApps.App.Run() fails to open the desired application and it stops the test). Is there a way to bypass or make the "Stop on Error" property ignore these scenarios? Because if TestComplete fails to open one of my applications, I would like to retry opening it and continue the test, but so far I have tried putting that code inside a "try-catch" (javascript) block, and the test is still stopped, ignoring the "try" block.

brumazz · Accepted Answer

It looks like it will work the same.
&nbsp;

I hope this helps.
If not I would suggest opening a support case.
&nbsp;

brumazz · Answer

What about changing the playback to retry failed test items?

&nbsp;

alexkaras · Answer

Hi,
&nbsp;
&gt;&nbsp;&nbsp;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.
&nbsp;

tcykpb · Answer

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&nbsp; find a workaround to make it open 100% of the times without errors).

brumazz · Answer

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.
&nbsp;

tcykpb · Answer

Hi&nbsp;brumazz&nbsp;, my code looks something like this:if not (Sys.WaitProcess("myapp.exe").Exists) {&nbsp; &nbsp; TestedApps.MyApp.Run() // &lt;--- Here Test Complete throws an error 4/10 times, and the execution is stopped even if I put it inside a try/catch}&nbsp;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.

Forum Discussion

How to avoid certain "Stop on Error" scenarios?

12 Replies

Related Content

'ClickCell' method has stopped working with error: "An error occurred"

Execute Scenario from AfterFeature function

Getting an error message "TF.EXE stopped working" when TFVC client is used for checkin

On Error - "Stop test item" is not working when I run a Mobile test using a Virtual Browser.

-- rerun failed scenarios

Recent Discussions

testcomplete feature Intelligent Quality Add Ons

SessionCreator /Timeout option not firing EventControl_OnTimeout

Object Browser does not display WPF DataGridCell Border

Issue with retrieving text from listbox items in desktop win32 application

Read data from Excel