You can generate HTML, PDF, or custom XSL reports. In this section:

A known bug in older versions of Eclipse may cause the IDE to crash when displaying reports. If you are experiencing this issue, here are some workarounds:

  • Update to the latest version of Eclipse.
  • Install a fixed XULRunner plugin to Eclipse.
  • Use an EPF (Eclipse Preferences File) to configure Eclipse to use an external browser; you need to change the  "browser-choice" option—e.g.,: /instance/org.eclipse.ui.browser/browser-choice=1
  • If the problem occurs only at the end of the testing process) Disable the Open in browser option in the Report and Publish dialog.

Generating Reports from the GUI

  1. After the test has completed, click the Generate Report button in the Test Progress panel’s toolbar.

  2. Complete the Report dialog that opens. The Report dialog allows you to configure the following options:

  3. Click OK. The report will then open. For details on the format and contents, see Understanding Reports.

You can also generate and configure reports from the bottom of the Test Progress panel.

Proceed immediately generates the report using the existing options.

Configure allows you to review and modify reporting options before generating the report.

Generating the Test Execution Details Report

You can generate an additional Test Execution Details report linked to your regular report (see Understanding Reports for details). To generate this report, configure the following settings in the test configuration before executing it:

  1. Choose Parasoft> Test Configurations...  and select a test configuration.
  2. Open the Execution> Runtime tab and enable the following options: 
  3. (Optional) Enable the Generate detailed coverage report for option and choose a coverage metric.
  4. Apply changes and close the test configuration.
  5. Choose Parasoft> Preferences... > Reports.
  6. In the Report Format section, choose HTML (C/C++test’s Unit Testing details) from the drop-down menu.

Click Generate Report after the test completes (see Generating the Report). The link to the Test Execution Details report will be available in the Test Execution Details column included in the Additional Reports section at the bottom of main report (see Understanding Reports).

You can also generate the Test Execution Details report in XML format. This enables you to apply additional post-processing workflows to the test execution results. The XML file is available in the same location as the original Test Execution Details HTML file, for example:



In addition, XML Schema for Test Execution Details XML file is available:


Uploading the Report to DTP

To upload the report to DTP:

Publishing reports to DTP requires the "DTP Publish" or "Automaton" license feature to be enabled.

Uploading the Report to Team Server

To upload the report to Team Server (Automation Edition only):

Team Server uses the following criteria to identify unique reports:

  • Host name

  • User name

  • Session tag

  • Day - each day, only the last test run is used in trend graph

If your team performs multiple cli runs per day—and you want all reports included on Team Server—you need to use a different session tag for each run. You can do this in the Test Configuration’s Common tab (using the Override Session Tag option).

Generating Reports from the Command Line

To generate a report of command line test results, use the -report %REPORT_FILE% option with your cli command.

To upload the report to Team Server, use the -publishteamserver option.

To upload the report to DTP, use the -publish option.

Command-line interface testing details are explained Testing from the Command Line Interface. This topic also discusses how to setup and configure email notifications.