Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space CPPTDESKDEV and version 10.4.2


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:

  • E-mail
  • Development Testing PlatformDTP
  • Project Center
  • License
  • Scope and Authorship
  • Source Control
  • Team Server


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.

Only top-level test suites (below) must be disabled for this setting to take effect.

Only top-level test suitesDetermines whether the Test Suite Summary report section only lists the .tst files (with this option enabled) or displays a tree-like view of the individual tests in each .tst file (with this option disabled). This is for SOAtest only.
Active static analysis rulesDetermines whether the report lists the static analysis rules that were enabled for the test.
Detailed report for [coverage metric]

Determines whether detailed coverage information is provided for the specified coverage metric. Select the desired coverage type from the drop-down list. 

Important: In order to generate a detailed coverage report, enable this option (and select the desired coverage metric) BEFORE running  tests.

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. 
titleHTML Report Hyperlinks for Requirement/Defect Details

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:


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


  • XML Schema: reports.xsd
  • Sample XML with a variety of results: rep_example.xml
    • Note that this report is used by all transformations below
  • Sample  transformation to a plain text CSV file
    • XSL file: csv.xsl
    • result: csv.txt
  • Sample transformation to an HTML table with a violations list
    • XSL file: html_table.xsl
    • result: html_table.html
  • Sample transformation to an HTML table with author/violations statistics
    • XSL file: stats_table.xsl
    • result: stats_table.html
  • Sample developer report transformation to a CSV file
    • XSL file: csv_dev.xsl
    • result: csv_dev.csv
  • Sample developer report transformation to an HTML file
    • XSL file: html_dev.xsl
    • result: html_dev.html