Skipping Test Item when the first error occurs

Hello Serglu,

I'm using TestComplete to stop the current test when it hits an error and proceed to the next one. You're on the right path using Event Handlers, set one up for OnLogError and in it, call Runner.Stop(True);

eg

function ProjectEvents1_OnLogEvent(Sender, LogParams)

 {

  Runner.Stop(True);

 }

http://support.smartbear.com/viewarticle/14191/

http://support.smartbear.com/viewarticle/12335/

Hello Bert,


The 'Stop on error - Test Item' option will stop the current test item's further iterations and child tests after the current test is finished.
It does not stop the current test when an error occurs. Have a look at these pages:

http://support.smartbear.com/viewarticle/11001/


http://support.smartbear.com/viewarticle/12329/

Cheers,



Jackson

The OnLogError event handler can be placed to a keyword test. See the Creating Event Handlers for TestComplete Events topic. In the event handler,  use the [url=http://support.smartbear.com/viewarticle/28075/]Stop Executionp/url] operation with the enabled 'Stop current test only' option

Use Runner.Stop(true) instead of Stop Execution. To call this method, use the Call Object Method operation

That is a setting in TestComplete.

1. Go to the test items page for TestComplete.


2. If you do not see the columns, stop on error, and stop on exception, right click somewhere and select field chooser to add them.


3. Select the behavior you want, in this case, Test Item, for each of the test items you want to stop on test item.


4. You probably also want to go to the playback properties and uncheck stop on error there.

Hi Bert,



I've read about that but from what I understood, it seems that if a test fails at the beginning, TC will continue to run the test until the end and only after all the steps of the test script are executed it will stop and continue to execute with the rest of the test items. 



So, this will not work for me. I need the execution of the failed test to stop at the first error and then continue with the rest of the test items from the suite.



The reason why I need this is because I have a suite of  time consuming tests. A test executes in about 10 mins, so you can imagine that if this test fails in the first 30 secs it will be redundant for me to continue executing that test for 9 min and 30 secs because the logs will be full of errors since the steps in my test depend on each other.



Can you offer me an alternative?



Thanks,

Vlad

If you set the test item to stop on error as I suggested, it does not continue the test item.  It goes to the next one.

Hi Bert,



I've tried this and it seems that if the test fails at the beginning, it continues to execute til the end of the test and logs errors for all the objects it didn't find in my application. (hundreds of errors for all the objects that were not found).



I would like to mention that your proposed solution is also the default behavior when you disable "Stop on error" from Project ->Properties->Playback.



Thus it runs the whole test redundantly, wasting time and then, indeed, jumps to the next test in the test suite.



Any ideas for my requested solution?



Thanks,

Vlad

Hi Jackson,



This is EXACTLY what I've been looking for!



That's right I've been planning to use OnLogError to handle the error by stopping the current test.



I've tried this and it works great.



Thanks a lot,

Vlad

Sergiu, you are correct that if you turn off Stop on Error in the playback, without subsequently setting Stop on Error for the individual Test Item, that TestComplete will continue after an initial error occurs.  The confusing thing here is that there are TWO places to specify Stop on Error.



The first place, you know about; in the playback settings for your project.  If that setting is checked, then the individual test item settings for stop on error are ignored.



There is, however, a second place where you can specify that the test should stop on error and that is on the Test Item page.  On the test item page, there are two columns, one for Stop On Error, and one for Stop on Exception.  These two columns are (stupidly in my opinion) hidden by default, which is why I said you need to use the Field Chooser to expose them.  Once you can see them, you can set each individual Test Item to stop its own execution, or stop execution of the entire project.



Here is a picture of the setting I am talking about.