This section describes exit codes that TestExecute returns. These codes report the result of the last test:
TestExecute supports the following exit codes. Normally, these codes are of use when TestExecute is launched from a batch file:
| Exit Code | Description | ||
|---|---|---|---|
| 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. | ||
| 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 15 Licensing Guide that is shipped with TestExecute.
To resolve licensing problems, please use the Licensing Troubleshooter on our web site: |
||
| Other codes | You may receive codes different from those above (for example, -10, -12). This can happen if your operating system, firewall, or a third-party application that manages TestExecute test runs overwrites the actual TestExecute exit code. In this case, to learn the received exit code definition, contact your system administrator or the SmartBear Support team. |
