The JavaTest harness provides information you can use in troubleshooting problems. To troubleshoot problems using the JavaTest harness see the following topics:
If the JavaTest harness fails, you can use the harness.trace
file
in your work directory to help 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 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 Test tabbed panes and the Configuration Editor to help determine the change required in the configuration.
The following is an example of how the Test Manager tabbed panes and the Configuration Editor 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 might have errors.
The following is an example of how the Test Manager tabbed panes can be used to identify and correct a test failure:
Most problems in viewing test results in the Test Manager result from the use of view filters (other than the All Tests view filter) with a current configuration set to run specific tests (such as, running tests based on their prior status). When a view filter other than All Tests is used in the Test Manager, only the fields of the filtered category appear to be updated in the Test Manager Summary tab. This is normal behavior of the GUI when view filters are used.
The JavaTest harness only displays tests in the GUI that match the specified view filter criteria. All other tests are displayed as Filtered Out.
As test results change, the JavaTest harness moves the tests to the Filtered Out category (not to a test result category) in the Test Manager and turns the appropriate node in the test tree gray. Consequently, the fields for the other categories in the Test Manager Summary tab might not appear to be updated.
Example:
If you change the current configuration to run only tests with a prior status
of Failed and use the Current Configuration view filter, the Test Manager displays
all tests that
are not a Failed status as Filtered Out. This allows you to monitor only those
tests with a previous Failed status. When you begin the test run, any tests
with Passed or Error results are displayed in the Filtered Out category
of the Test Manager. To view the actual test results, change
to
a different view filter. See Using View
Filters for a detailed description
of the view filters.
If one of the output streams
in the Test Run Messages Pane displays the following message, restart
the JavaTest harness with the harness VM system property JavaTest
harness.maxOutputSize
value
set to a greater number and rerun the test to ensure
that all of the data is saved.
Output overflow:JavaTest harness has limited the test output of the text
to that at the beginning and the end, so that you can see how the
test began, and how it completed.
If you need to see more of the output from the test,
set the system property JavaTest harness.maxOutputSize to a higher
value. The current value is 100000
Set the system property of JavaTest harness.maxOutputSize by using the syntax in
java -DJavaTest harness.maxOutputSize=200000 -jar lib/JavaTest harness.jar ....
The value of the system property sets the number of characters to accept.
The value of the system property is an integer subject to the maximum integer size of the VM.
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. See Creating Reports for detailed information.
Filters are used to write test reports for a specific set of test criteria. Verify that you are using the appropriate filter to generate reports of test results. See Creating Reports for detailed information.
Test reports contain relative and fixed links to other files that might 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. See the JavaTest Harness User's Guide: Command-Line
Interface.