Stop Current Test Item on the N-th Error

Applies to TestComplete 15.69, last modified on November 13, 2024

Errors that occur during the test run can be caused by accidental reasons. Such errors can occur a few times, and you may not want to interrupt your tests because of them. However, if a number of errors exceeds some limit, it will mean that something goes wrong and the test item should be stopped.

To configure your project to stop a test item when an error limit is reached and proceed with the next sibling test item:

Note: The approach we describe uses the Log.ErrCount property that returns the number of errors that are posted during the current test item. To get the number of errors occurred during the entire project run, create and use a project variable as an error counter. To learn more about this approach, see Stop Project Run on the N-th Error.

  1. If your project does not have the Events collection, add it:

    Add the Events collection to your project

    Add an event control to the Events collection and create a handler for the OnLogError event:

    Add the OnLogError event handler
  2. Configure the event handler to compare the number of occurred errors with the number of “allowed” errors and stop the test item, if needed.

    • If you use scripts

      Add the following code to the event handling routine:

      Show Code

    • If you use keyword tests

      Show Instructions

  3. Open the Execution Plan editor of the project and make sure that the On error property of all your test items are set to Continue running. Otherwise, TestComplete will stop the entire test run on the first error.

    Configure test items to Continue running

    The Runner.Stop(true) script method and the Stop Execution operation stop the test item even if you set On error to Continue running. TestComplete will not run the test item’s further iterations and child test items.

See Also

Execution Plan Editor
Tests, Test Items, and Test Cases
StopOnError Property
StopOnException Property
Running Tests
Stopping Tests on Timeout

Highlight search results