...
| Setting | Purpose | ||||||
|---|---|---|---|---|---|---|---|
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 maximum length for a build ID is 128 characters. The default is The following configuration specifies the custom build ID that consists of the name of the project and the build number passed via the environmental variable
For the ABC project and the build number 114 on a CI server, this may resolve to | ||||||
report.active_rules=true|false | Determines if the reports contain a list of the rules that were enabled for the test. Default: false | ||||||
report.archive=true|false | Enables the generation of 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, PDF, SARIF, 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. Default: false | ||||||
report.associations | Specifies whether the report shows requirements, defects, tasks, and feature requests that are associated with a test. Default: false | ||||||
report.authors_details | Determines whether the report includes an overview of the number and type of tasks assigned to each team member. Default: true | ||||||
report.contexts_details | Determines whether the report includes an overview of the files that were checked or executed during testing. Default: false | ||||||
| Specifies the location and extension of the XSL file for a custom format. Used with For details and examples, see Configuring Reporting Settings. | ||||||
report.developer_errors=true|false | Determines whether manager reports include details about team member tasks. Default: false | ||||||
report.developer_reports=true|false | Determines whether the system generates detailed reports for all team members (in addition to a summary report for managers). Default: true | ||||||
| Specifies whether the tested source code is published to the DTP server. If set to If set to If set to Default: full (Default when the report.dtp.publish option is enabled.) | ||||||
| Specifies the report formats. To generate multiple reports in different formats for a single run, enter a comma-separated list. If you have the "Automation" license feature enabled, XML reports are generated and saved in addition to the report formats specified. For example:
Default: html | ||||||
report.mail.attachments=true|false | Determines whether reports are sent as attachments. All components are included as attachments; before you can view an HTML report with images, all attachments must be saved to the disk. Default: false | ||||||
report.mail.cc=[email_addresses] | Specifies where to mail comprehensive manager reports. This setting must be followed by a semicolon-separated list of email addresses. This setting is typically used to send reports to managers or architects. It can also be used to send comprehensive reports to team members if such reports are not sent automatically (for example, because the team is not using a supported source control system). | ||||||
report.mail.compact=trends|links | Specifies that you want to email a compact report or link rather than a complete report. If If | ||||||
report.mail.domain=[domain] | Specifies the mail domain used to send reports. | ||||||
report.mail.enabled=true|false | Determines whether reports are emailed to team members and to the additional recipients specified with the Remember that each developer that worked on project code will automatically be sent a report that contains only the errors/results related to his or her work. Default: false | ||||||
report.mail.exclude=[email_addresses] | Specifies any email addresses you do not want to receive reports. This set-ting is used to prevent automated sending of reports to someone that worked on the code, but should not be receiving reports. | ||||||
report.mail.exclude.developers=true|false | Specifies whether reports should be mailed to any team member whose email is not explicitly listed in the Default: false | ||||||
report.mail.format=html|ascii | Specifies the email format. Default: html | ||||||
report.mail.from=[email_address OR user_name_of_the_same_domain] | Specifies the "from" line of the emails sent. Default: | ||||||
report.mail.include=[email_addresses] | Specifies the email addresses of team members that you want to receive individual reports. This setting must be followed by a semicolon-separated list of email addresses. This setting is typically used to send individual reports to team members if such reports are not sent automatically (for example, because the team is not using a supported source control system). It overrides team members specified in the 'exclude' list. | ||||||
report.mail.on.error.only=true|false | Determines whether reports are sent to the manager only if a task is generated or a fatal exception occurs. Team member emails are not affected by this setting; individual emails are sent only to team members who are responsible for reported tasks. Default: false | ||||||
report.mail.server=[server] | Specifies the mail server used to send reports. | ||||||
report.mail.port=[port] | Specifies the mail server host’s port number. Default: 25 | ||||||
report.mail.security=[SL| STARTTLS| NONE] | Specifies the desired security. Available settings are SSL, STARTTLS, NONE. SSL is not available in Visual Studio. | ||||||
report.mail.subject=My New Subject | Specifies the subject line of the emails sent. The default subject line is ${tool_name} Report - ${config_name}. For example, if you want to change the subject line to "Report for Project A", you would use
Default: | ||||||
report.mail.time_delay=[server] | Specifies a time delay between emailing reports (to avoid bulk email restrictions). Default: 0 | ||||||
report.mail.unknown=[email_address OR user_name_of_the_same_domain] | Specifies where to mail reports for errors assigned to "unknown". | ||||||
report.mail.username=[username] report.mail.password=[password] report.mail.realm=[realm] | Specifies the settings for SMTP server authentication. The | ||||||
report.metrics_details=true|false | Determines whether an XML report with metrics summary information (as well as individual class and method detail data where applicable) is produced. This report will be generated only when a metrics-enabled Test Configuration is run. Metrics details will be shown in HTML and PDF reports. Default: true | ||||||
report.ref.report.file=[path] | Specifies a path to the location where the reference report file will be created during analysis. See Configuring Task Reporting Preferences. | ||||||
report.additional.report.dir=[directory] | Specifies a path to the directory where additional C/C++test Standard-compatible XML report files will be generated for the currently executed test configuration. The additional XML report files may include static analysis, metrics, unit testing and line coverage results, depending on the test configuration. This setting is available only in the command line mode (CLI). | ||||||
report.rules=[url_path_to_rules_directory] | This setting specifies a path to the directory containing static analysis rules HTML files. Based on that path, links to rule documentation are added in HTML reports. To apply this setting in the GUI, you need to define it in a .properties file and then provide a path to this file in the Option file field in the Report & Publish window. For more details, see Generating Reports. For example:
Default: none | ||||||
| Specifies if and how much additional information from source control is included in the report. If set to If set to If set to Default: off | ||||||
report.setup.problems=top|bottom|hidden | Determines whether reports include a section about setup problems.
Default: bottom | ||||||
report.suppressed_msgs=true|false | Determines whether reports include suppressed messages. Default: false | ||||||
report.test_params=true|false | Determines whether reports include test parameter details. Default: false | ||||||
| This setting specifies a custom parameter Id to be added to the xml report root element. The Id needs to be unique. Both For example, the following configuration specifies that an attribute with the given key and value will be added to the xml report root element:
| ||||||
| This setting specifies a custom parameter value to be added to the xml report root element. Both For example, the following configuration specifies that an attribute with the given key and value will be added to the xml report root element:
| ||||||
report.ue_coverage_details_htmls=[coverage_type] | Determines whether a test's HTML report links to another report that includes source code annotated with line-by-line coverage details. The following values can be used for [coverage_type]: LC - for line coverage | ||||||
session.tag=[name] | Specifies a session tag used to label these results. This value is used for uploading summary results to DTP. The tag is an identifier of the module checked during the analysis process. Reports for different modules should be marked with different tags. Default: | ||||||
tasks.source.control.details=true|false | This setting specifies if additional information from source control, such as revisions and comments, is included in the report. |
...