Handling the Error 'The test run has stopped...'

During the test run, various messages can be posted to the test log. TestComplete includes several settings that control whether the test run should stop once an error message (or a warning) is posted to the log.

1. Open the test log and locate the “The test run has stopped...” message in it.

2. The “The test run has stopped...” message is posted right after an error is posted to the log. So, to see what event caused the “The test run has stopped...” message, just look at the previous message in the log.

3. Examine the description that is shown in the Details panel for the problematic message to understand the cause of the problem.

   To view the test commands that posted the error message, double-click that message in the test log. TestComplete will open the test containing the problematic command and will highlight that command in the test.

Usually, test commands posts errors if they cannot find the needed tested object. For example, if a test command gets a test process or window and the process or window does not exist, the command will post an error message informing about the problem.

Example

ExampleExample

For example, the following sample code activates a form of a tested application. If the tested application is not running, or if the tested form does not exist, the code will post the “Object Not Found” error. If your project is configured to stop tests whenever an error message is posted to the test log, the test run will stop.

JavaScript, JScript

Python

VBScript

DelphiScript

C++Script, C#Script

Copy Code

JavaScript, JScript

Aliases.MyApp.Form1.Activate();
// OR
Sys.Process("MyApp").Window("Form1").Activate();

Python

  Aliases.MyApp.Form1.Activate();
  # OR
  Sys.Process("MyApp").Window("Form1").Activate();

VBScript

Aliases.MyApp.Form1.Activate
' OR
Sys.Process("MyApp").Window("Form1").Activate

DelphiScript

Aliases.MyApp.Form1.Activate();
// OR
Sys.Process('MyApp').Window('Form1').Activate();

C++Script, C#Script

Aliases["MyApp"]["Form1"]("Activate")();
// OR
Sys["Process"]("MyApp")["Window"]("Form1")["Activate"]();

To avoid interrupting your tests, you can do the following:

• (Recommended) Update your test so that it handles the occurred errors properly.

  For example, if your test is not able to find the needed test object, update the test to wait for the object:

  Waiting for an Object, Process or Window Activation

  Checking Whether an Object Exists

  Waiting for Object State Changes

• If you do not want the test run to stop when an error occurs, do the following:

  • If you run your test as a test item, set its On error property to Continue running.

  • If you run your test from Project Explorer, set the Error handling > On error project property to Continue running.

• If you do not want the test run to stop when a warning occurs, set the Error handling > On warning project property to Continue running.

• To prevent your test from stopping when TestComplete cannot find a tested object referred by its full name, you may also want to make sure that the Handling errors > On object recognition error property is set to Continue running.