This topic explains how to configure reporting settings. Reporting settings can be configured in the GUI or from the command line interface (using localsettings).

Sections include:

From the GUI

The available GUI controls can be used to specify reporting settings for all tests—whether they are run from the command-line interface or the UI. 

Before configuring report settings, you should review the settings on the following preference pages to ensure that the task authorship is being calculated correctly, results are being sent to the proper Team Server and Parasoft Project Center server, the correct email host is used, and so on:

The settings specified in the UI can be fully or partially overwritten by those specified via localsettings.

To specify reporting settings from the GUI:

  1. Choose Parasoft> Preferences. The Preferences dialog will open.
  2. Select  Parasoft> Reports.
  3. Specify the appropriate settings. Available settings are described in Report Configuration Settings below.
  4. If you have not already configured e-mail settings (sender address, host name, etc.) in either the GUI or from the command line, do so now in Parasoft> E-mail.
  5. Select  Parasoft> Reports> E-mail Notifications.
  6. Specify the appropriate e-mail notification settings. Available settings include:

Report Configuration Settings

Reports Content

Detailed report for developersDetermines whether customized, detailed  reports are generated for each team member (in addition to a summary report for managers). These reports contain only the tasks assigned to that specific team member.
Overview of tasks by authorsDetermines whether the report includes an overview of the number and type of tasks assigned to each developer.
Overview of checked files and executed tests

Specifies whether the report provides details about all checked files and executed tests. 

For static analysis, this results in a list of all the files that were checked. For each file, it lists the number of rule violations and the number of suppressed violations. If the file has a violation, it also lists the line number, rule name, and rule ID for that violation.

For test execution, this results in a  list of all executed test cases and their outcomes (pass or fail). For each test suite, it lists the total number of test cases and the number of passed test cases. If a task is reported for a test case, additional details (stack trace, outcome, etc.) are presented.

For code review, this results in a list of all pending issues with messages between author - reviewer - monitor (filtered by session tag by default).

Task detailsDetermines whether the report includes details about all of the reported tasks.
Test case detailsDetermines whether the report includes details about all executed test cases.
Suppression detailsSpecifies whether the report lists suppressed messages.
Requirement/defect details

Specifies whether the report shows requirements, defects, tasks, and feature requests that are associated with a test.

Active static analysis rulesDetermines whether the report lists the static analysis rules that were enabled for the test.
Only tests that failedSpecifies whether the report lists only tests that failed.
Generate formatted reports in command-line modeDetermines whether formatted reports are generated for tests run in command line mode.
Cutoff date for graphsSpecifies the start date for trend graphs that track different categories of tasks over a period of time. 

If you are specifying a URL for the artifact (e.g., as a C/C++test test property), that URL will be available as a hyperlink in HTML reports. 

If want to create hyperlinks and you are specifying artifact associations using only the artifact ID as specified in Change-based Testing and Traceability, you can use local properties to specify how the ID maps to a URL.

For example:

Report Format


Specifies the desired report format:

  • HTML - includes XML source data file
  • PDF
  • XML SATE - format specific to NIST SAMATE Static Analysis Tool Exposition
  • XSL Custom
  • xUnit - a format that is like JUnit, with the addition of nested test suites. This format is supported by Jenkins, Hudson, Eclipse JUnit view, etc.. It is applicable only with Overview of checked files and executed tests enabled.
XSL fileIf you chose custom XSL as the report format, specify the path to the XSL file that defines your custom format. 
Report file extensionIf you want to use a file extension other than the default .html extension, specify that extension here.
Generate additional archive with entire report content

Enable this option to generate an additional compressed archive (.zip) file in the specified report location. The ZIP file contains all the files generated to build the report. 

This option can generate an archive for any report format (e.g., HTML, CSV, PDF, etc.). 

By generating an archive, you can also perform custom transformations of the report because all of the elements are generated to the specified destination folder.

Advanced Settings

Add absolute file paths to XML dataSpecifies whether absolute file paths are added to XML data. This needs to be enabled on the Server installation if you want to relocate tasks upon import to desktop installations (as described in Relocating Tasks During Import: Requirements and Limitations). 
Add metric details to XML data:Specifies whether type-level and method-level metrics details are added to the XML report (in addition to project and package/namespace-level details, which are included by default). Metrics details will be shown in HTML and PDF reports.
Session tagSpecifies a tag for this report. This value is used for uploading summary results to Team Server. The results from each of the team’s regular test runs should have a unique tag. Variables can be used as described in  Using Preference Settings for Command-Line Execution. For instance, if your team runs static analysis, unit testing, and code review, you might use the session tags Static, Execution, and Code Review. Or, you might use variables such as session.tag=${config_name} or session.tag=${analysis_type}

From localsettings

Reporting options can be specified in localsettings (e.g. for sharing team-wide settings via DTP or specifying options at the command line). See Configuring Localsettings for details. 

Support for Custom Report Formats

You can customize locally-generated and emailed reports by building a custom XSL transformer that specifies how you want the results formatted. For instance, you could use a custom transformer to map data into the format you need to demonstrate compliance to an internal security policy.

To specify a custom report format, you need to:

  1. Create an XSL file that specifies how you want to transform the XML data.
  2. In the Preferences panel’s Reports page, specify the location of this XSL file, as well as the extension that should be assigned to the resulting file.

Available Parameters

The following parameters can be used in custom XSL files:

report_type=disk_report|email_reportDetermines if the generated report will be sent by email or saved on the local disk drive. 

The command line that was used to start the product that generated this report.

Example: cpptestcli: -config team:// -localsettings /home/nightly/ -publish -report /home/nightly/reports/report.html -resource myproject -dtp.autoconfig [email protected]:8080 


The name of the Test Configuration that was executed to produce this report.
Example: Parasoft's Recommended Rules


The directory where the report is created. This can be used to generate developer reports.

Example: <xsl:value-of select="concat($output_dir,$dev_reports_prefix,$authid,'.csv')"/> 


The directory where rules documentation is saved. This can be used to generate rule popups/links.

Example: <xsl:value-of select="concat('javascript:openWin(',$qt,$rules_dir_path,$id,'.html',$qt,')')"/> 

suppr_msgs=true|falseThe value of the "Suppressions details" option. See Report Configuration Settings for details.
dev_errors=true|falseThe value of the "Task details" option. See Report Configuration Settings for details.
dev_reports=true|falseThe value of the "Detailed report for developers" option. See Report Configuration Settings for details.
show_active_rules=true|falseThe value of the "Active static analysis rules" option. See Report Configuration Settings for details.
associations=true|falseThe value of the "Requirement/defect details" option. See Report Configuration Settings for details.

The prefix used to name developer reports.

Example: <xsl:value-of select="concat($output_dir,$dev_reports_prefix,$authid,'.csv')"/>


The value of the "Detailed report for" option. See Report Configuration Settings for details.

attachments=true|falseThe value of the localsettings key report.mail.attachments. See Configuring Localsettings for details.

The value of the localsettings key report.test_suites_only. See Configuring Localsettings for details.

test_cases_details=true|falseThe value of the "Test case details" option. See Report Configuration Settings for details.
failed_tests_only=true|falseThe value of localsettings key report.failed_tests_only. See Configuring Localsettings for details.
authors_details=true|falseThe value of the "Overview of tasks by authors" option. See Report Configuration Settings for details.
contexts_details=true|falseThe value of the "Overview of checked files and executed tests" option. See Report Configuration Settings for details.


For additional guidance, see the following files:

Local Reports