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

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:

    • Preferences: See Configuring Reporting Settings.

    • Options file: If you want to override the report settings specified in the GUI’s Preferences panel, you can specify a .properties file configured with your custom report settings; see Configuring Localsettings.

    • Report location: Specify where to output the report file. By default, reports are created in the <user_home_dir>\Local Settings\Temp\parasoft\xtest directory.

    • Open in browser: Enable/disable opening the report file in the browser automatically.

    • Delete on exit: Enable/disable deleting the report upon exiting C/C++test.

    • Generate reports: Enable/disable generating a report. You cannot proceed if this setting is disabled.

    • Publish reports to Team Server: Enable this option only if you are using Team Server to manage shared reports and configurations.

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


Alternatively, you can generate and configure reports from the bottom of the Test Progress panel.

  • Click Proceed to immediately generate the report using the existing options.
  • Click Configure to review or 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: 
    • Report unit test execution details
    • Include tasks details
    • Include passed assertion details 
    • Generate detailed test execution report 
  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 Reports to DTP

To upload the report to DTP:

  • Ensure that C++test is connected with a DTP Server (See Connecting to DTP).

  • Go to Parasoft> Preferences... > DTP and enable the Enable reporting results to DTP option.

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

Generating Reports from the Command Line

  • Use the -report %REPORT_FILE% command line option to generate a report for command line execution.
  • Use the the -publish option to upload the report to DTP (or the -publishteamserver option if you use Team Server to manage reports).

See Testing from the Command Line Interface for details about executing tests from the command line interface and configuring email notifications.

How do I aggregate or separate results from multiple test runs on Team Server?

If you report results to Team Server,  the following criteria are used 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).

  • No labels