Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2022.1

...

SettingDescription
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). 
Session TagSession tags are unique identifiers for test runs and are used to distinguish specific runs from similar runs in DTP. 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}
Build ID

Specifies a build identifier used to label results. It may be unique for each build but may also label more than one test sessions that were executed during a specified build.

The default is ${dtp_project}-${time}.

From Settings

See Reporting Settings for details. 

Anchor
Legacy Report Format
Legacy Report Format
Legacy Report Format

...

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:

Code Block
languagetext
soatestcli -config team://xtest-static.properties^
 -settings /home/nightly/settings.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,')')"/> 

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 settings key report.mail.attachments. See Configuring Settings for details.
test_suites_only=true|false

The value of the settings key report.test_suites_only. See Configuring Settings 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 settings key report.failed_tests_only. See Configuring Settings 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.