TestExecute supports the same exit codes as TestComplete does. These codes report the result of the last test:
|0||The last test did not produce errors or warnings.|
|1||The last test results include warnings but no errors.|
|2||The last test results include errors.|
The test cannot be run because of an error. Some typical errors are:
The test engine also returns the code 3, if you run a project or project suite and the test was stopped with a call to the
|4||The test run was stopped by the timeout specified with the
|127||Unable to launch TestExecute, because some TestExecute files are missing or the installation is damaged.|
|1000||Unable to launch TestExecute, because another instance of TestExecute is already running.|
|1001||Unable to start TestExecute, because there is not enough free disk space.|
|-1||Unable to launch TestExecute because the license check has failed and TestExecute cannot obtain a license.
You can find information on TestExecute licensing in TestExecute 14 Licensing Guide that is shipped with TestExecute.
To resolve licensing problems, please use the Licensing Troubleshooter on our web site:
Normally, these codes are of use when TestExecute is launched from a batch file. Here is a simple example:
|Note:||The following example uses the 32-bit version of TestExecute. If you use the 64-bit version, the TestExecute executable is located in the <TestExecute>\x64\Bin folder.|
|When launching TestExecute from a command line or batch file, it is not recommended to use the RunAs command, since this will significantly slow down the script execution.|