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

Applies to TestComplete 15.47, last modified on January 20, 2023

About the Message

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.

Diagnosing the Problem

  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.

Resolving the Problem

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

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

See Also

Handling Playback Errors
Common Tasks
About Controlling Test Execution Flow

Highlight search results