The JavaTest harness provides information in the following topics that you can use to troubleshoot problems:
When the JavaTest harness exits, it displays an exit code that you can use to determine the exit state. The following table contains a detailed description of the exit codes.
Exit Code | Description |
---|---|
0 | If tests were executed, all tests passed. |
1 | One or more tests were executed and failed. |
2 | One or more tests were executed and had errors. |
3 | There was a problem with the command-line arguments. |
4 | JavaTest harness internal error. |
If the JavaTest harness fails, you can use the
harness.trace
file in your work directory to troubleshoot the problem. The
harness.trace
file is a plain-text file that contains a log of JavaTest harness activities during the test run. It is written in the work directory, is incrementally updated, and is intended primarily as a log of JavaTest harness activity.
The goal of a test run is for all tests in the test suite that are not filtered out to have passing results.
If the root test suite folder contains tests with errors or failing results, you must troubleshoot and correct the cause to satisfactorily complete the test run. See Troubleshooting a Test Run in the JavaTest Harness User's Guide: Graphical User Interface for information about the resources that the JavaTest harness provides for troubleshooting.
Tests with errors are tests that could not be executed by the JavaTest harness. These errors usually occur because the test environment is not properly configured. Use the GUI Test tabbed panes and configuration editor window to help determine the change required in the configuration.
The following is an example of how the GUI Test Manager tabbed panes and the configuration editor window can be used to identify and correct a configuration error:
Tests that fail are tests that were executed but had failing results. The test or the implementation may have errors.
The following is an example of how the GUI Test Manager tabbed panes can be used to identify and correct a test failure:
The JavaTest harness does not automatically generate reports of test results after a test run. You must generate test reports either from the command line or from the JavaTest harness GUI.
You use filters to write test reports for a specific set of test criteria. See Creating Reports in the JavaTest Harness User's Guide: Graphical User Interface. Verify that you are using the appropriate filter to generate reports of test results.
Test reports contain relative and fixed links to other files that may be broken when you move reports to other directories.
You must update these links when moving reports to other directories. The JavaTest harness provides an EditLinks utility that updates the links in the reports for you when moving reports.