Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SettingDescription
Format

Specifies the desired report format:

  • HTML - includes XML source data file
  • PDF
  • SARIF (Static Analysis Results Interchange Format)
  • 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.

...

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

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

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

test_config_name

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

output_dir=[dir]

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')"/> 

rules_dir_path=[path]

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.
dev_reports_prefix=[prefix]

The prefix used to name developer reports.

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

exec_cvg_details=true|false

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.test_suites_only=true|falseThe 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.

...