Viewing a Report of Results

Jtest generates the following types of reports:

• Single Class Report
• Project Report
• Detailed Project Report
• Summary Project Report

These reports all use the standard JNI 1.1 specification to identify methods.

By default, the reports are formatted in text (ASCII) format. If you would like Jtest to generate HTML reports (e.g., if you want to post the report on your development intranet), choose Preferences> Configuration Options> Report Format> HTML.

Single Class Report

After performing a test on a single class, Jtest will generate a Single Class Report of the testing session.

This report contains, among other information, the annotated source code for the tested class. This may be used to determine what lines Jtest tested and what lines it did not test. Lines of code that were not tested are marked with a ">" at the beginning of the line; absence of the ">" indicates that a line was tested.

To access the Single Class Report, click the Report button in the Class Testing UI tool bar.

By default, Jtest does not show the source of every accessed class unless you tell it to do so. Use the Preferences> Configuration Options> Report File> Show All Classes Accessed option to tell Jtest to display the annotated source of each class accessed by the class under test. Also, Jtest does not, by default, show the test cases used for the test. Use the Preferences> Configuration Options> Report File> Show Test Cases option to tell Jtest to include test case information in this report.

If you would like a Single Class Report for a class included in a project test, open the class in the Class Testing UI, then click the Report button.

Summary Project Report

This is the least detailed of the three available project reports. This report contains the test name and a one line report of each error available in the Results panel; if there are no errors, this report contains only the test name.

To access the Summary Project Report, right-click the Report button in the Project Testing UI tool bar, then choose View Summary Report from the shortcut menu; you can also obtain this report by using -summary_report in the command line.

All project reports contain only information on the classes and errors that were available in the Results panel when the Report button was clicked. To limit the classes and errors contained in your report, display only the desired classes and errors in the Results panel before you click the Report button.

Project Report

This report is more detailed than the Summary Project Report, but less detailed than the Detailed Project Report. This report contains project test parameters as well as all essential details about each error available in the Results panel.

To access the Project Report, click the Report button in the Project Testing UI tool bar, or use -report at the command line.

All project reports contain only information on the classes and errors that were available in the Results panel when the Report button was clicked. To limit the classes and errors contained in your report, display only the desired classes and errors in the Results panel before you click the Report button.

Detailed Project Report

This is the most detailed of the three available project reports. This report contains project test parameters, class test parameters, and all results information available in the Results panel.

To access the Detailed Project Report, right-click the Report button in the Project Testing UI tool bar, then choose View Detail Report from the shortcut menu; you can also obtain this report by using -detail_report in the command line.

All project reports contain only information on the classes and errors that were available in the Results panel when the Report button was clicked. To limit the classes and errors contained in your report, display only the desired classes and errors in the Results panel before you click the Report button.