In this section:
This setting specifies a tag for signing results from the test session. The tag is a unique identifier for the specified analysis process made on a specified module. Reports for different test sessions should be marked with different session tags.
You can create a tag using a string of characters, as well as the variables (see Using Variables).
|[tag name]||A unique tag that identifies results from different sessions. The default is |
The default session tag includes variables that specify the source control branch name and the execution environment. For example, if source control integration is not configured, and the test session is performed on a 64-bit Windows, the report will include a session tag that may look as follows:
The following configuration specifies a tag other than the default:
This setting 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.
|[id]||An id that is used to label results. The default is |
The default build ID includes the name of the project in DTP and the date of the build. For example, for the ATM project, the build ID included in the report may resemble the following: ATM2-2017-07-07.
The following configuration specifies the custom
This setting specifies a custom name for the project's module. The setting may be used to describe unique runs. If unspecified, the tested module is detected automatically based on the analyzed code.
|[name]||A name of the project module.|
The following configuration specifies the custom XTests module name:
This setting specifies a list of tags that describe the environment where the run was executed. Tags may describe the operating system (e.g., Windows, Linux), architecture (e.g., x86, x86_64), compiler, browser, etc. The exec.env tags enable the entire session to be described. A detailed description of the environment may also be included in the test suite, test, or test case levels via services API.
|[tag1;tag2...]||A list of tags that describe the execution environment separated with a semi-colon.|
The following configuration specifies three tags:
This setting specifies the directory where the report will be created.
|[path]||A path to the directory where the reports are created.|
The following configuration specifies the path to the
This setting specifies the report format. Use a comma separated list of formats to reports in more than one format.
|xml||Default. Generates a report in the XML format.|
|html||Default. Generates a report in the HTML format.|
|Generates a report in the PDF format.|
|csv||Generates a report in the CSV format.|
|custom||Generates a report in a custom format; see report.custom.extension and report.custom.xsl.file.|
The following configuration specifies the PDF report format:
This setting specifies the report file extension of the XSL file for a custom format. It requires the report.format option to be set to
custom, as well as report.custom.xsl.file to be configured.
|[extension]||A custom extension of the XSL file.|
This setting specifies the location of the XSL file for a custom format.
|[path]||A path to the XSL file.|
This setting specifies whether manager reports will include details about developer errors.
|true||Details about developer errors are included in the report.|
|false||Default. Details about developer errors are not included in the report.|
The following configuration enables including details about developer errors in the report:
This setting specifies whether the system generates detailed reports for all developers (in addition to the summary report for managers).
|true||Enables generating detailed reports for developers.|
|false||Default. Disables generating detailed reports for developers.|
The following configuration enables generating detailed reports for developers:
This setting specifies whether the report includes an overview of the number and type of tasks assigned to each developer.
|true||Default. Reports include types and numbers of tasks assigned to each developer.|
|false||Reports do not include types and numbers of tasks assigned to each developer.|
The following configuration disables including details about numbers and types of tasks for each developer:
This setting specifies whether the report includes an overview of the files that were checked or executed during analysis.
|true||Default. Reports include a list of files that were checked.|
|false||Reports do not include a list of files that were checked.|
The following configuration disables including a list of files that were checked.
This setting specifies whether the report includes suppressed messages.
|true||Suppressed messages are included in the report.|
|false||Default. Suppressed messages are not included in the report.|
The following configuration enables including suppressed messages:
This setting specifies whether additional metadata about findings should be downloaded from DTP. Only the findings that are already available on DTP are affected. The DTP server must also support the metadata service for this setting to take effect.
|true||Default. Metadata about findings are downloaded from DTP.|
|false||Metadata about findings are downloaded from DTP.|
The following configuration disables downloading additional metadata from DTP:
This setting specifies if and how much additional information from source control is included in the report.
|off||Default. Information from source control is not included in the report.|
|min||The report includes information about repositories, file paths, and revisions.|
|full||The report includes information about repositories, file paths, and revisions, as well as task revisions and comments.|
The following configuration enables including information about repositories, file paths, and revisions in the report:
This setting enables or disables showing requirements, defects, tasks, and feature requests associated with a test in the report.
|true||Default. Requirements, tasks and feature requests are included in the report.|
|false||Requirements, tasks and feature requests are not included in the report.|
The following configuration disables showing requirements, tasks and feature requests in the report:
This setting specifies a list of issue tracking tags.
A comma-separated list of tags. The following tags are supported by default:
This setting generates a link to an association inside the HTML report. The URL is a query string containing an [%ID%] placeholder for the
The link to the association that will be included in the HTML report.
This setting specifies if the report contains a list of the rules that were enabled during analysis.
|true||Default. The list of active rules is included in the report.|
|false||The report does not include the list of active rules.|
The following configuration disables showing the rules that were enabled during analysis in the report:
This setting specifies a directory for storing static analysis rules HTML files (retrieved by clicking the Printable Docs button in the Test Configuration's Static Analysis tab).
The location where the HTML static analysis rule files are stored.
This setting specifies whether the report includes test parameter details.
|true||Default. The parameter details are included in the report.|
|false||The parameter details are not included in the report.|
This setting enables or disables including details about specific Google Test assertion failures in the HTML report.
Google Test assertion failures are included in the report.
Google Test assertion failures are not included in the report.
The following configuration enables showing Google Test Assertion failures:
This setting specifies a set of tags that will be used to create coverage images in DTP. DTP supports up to 3 coverage images per report.
A semicolon-separated list of tags that will be used when coverage images are created in DTP.
This setting that specifies the lower coverage threshold. Coverage results lower than the specified value are highlighted in the report.
A value that represents the lower coverage limit. The default value is
The following configuration sets the lower coverage value to 50:
This setting specifies a list of additional attributes for metric results.
A list of comma-separated attributes. The following attributes are supported by default:
This setting enables or disables archiving reports into a ZIP file.
|true||Reports are archived in a ZIP file.|
|false||Reports are not archived in a ZIP file.|
This setting specifies the start date for trend graphs that track static analysis task, test execution, and coverage. Requires configuring the
A date in the month-day-year format.
This setting specifies the duration from the start date for trend graphs that track static analysis task, test execution, and coverage. Requires configuring the
Specifies the duration in the days-months-years format.
This setting enables or disables report emails to developers and additional recipients specified with the
|true||Developers and additional recipients are automatically sent a report that contains the errors/results related to his or her work.|
|false||Default. Developers and additional recipients are not sent the reports.|
This setting specifies the mail server used to send reports.
The host name of the server where the report will be sent.
This setting specifies the port for SMTP server.
The port number. The default is
This setting specifies SMTP server connection security.
|STARTTLS||Default. STARTTLS connections security is used.|
|SSL||SSL connections security is used.|
This setting specifies the subject line of the emails that are sent.
The subject of the email.
report.mail.subject=ABC Project Results
These settings specify required information for SMTP server authentication. The realm value is required only for those servers that authenticate using SASL realm.
This setting specifies the mail domain used to send reports.
The domain where the reports are sent.
This setting specifies a delay between emailing reports (to avoid bulk email restrictions).
The reports will be emailed with the specified time delay.
This setting specifies the content of the "from" field of the emails sent.
|[email]||The "from" field will include the email address|
|[user]||The "from" field will include the user name.|
This setting enables or disables sending reports as attachments. All components are included as attachments; before you can view a report with images, all attachments must be saved to the disk.
|true||The emails will be sent with attachments.|
|false||The emails will be sent without attachments.|
This setting specifies how the report information is delivered in the email. This setting is not configured by default.
|trends||The email contains a trend graph, summary tables, and other compact data; detailed data is not included|
|links||The email only contains a link to a report available on DTP server.|
This setting specifies the content type for the email.
|html||The email content has the HTML format.|
|ascii||The email content has the ASCII format.|
This setting specifies email address for sending comprehensive manager reports. Multiple addresses must be separated with a semicolon. This setting is commonly used to send reports to managers or architects, as well as select developers.
A list of email addresses separated by semi-colons.
[email protected];[email protected]
This setting specifies email addresses of developers that you want to receive developer reports. Multiple addresses must be separated by a semicolon. This setting is commonly used to send developer reports to developers if developer reports are not sent automatically (e.g., because the team is not using a supported source control system).
This setting overrides addresses specified in the 'exclude' list.
A list of email addresses separated by semi-colons.
This setting specifies email addresses that should be excluded from automatically receiving reports.
A list of email addresses separated by semicolons.
This setting enables or disables report emails to developers who are not explicitly listed in the
report.mail.cc setting. This setting is used to prevent reports from being mailed to individual developers.
|true||Emails will not be sent to developers who are not explicitly specified.|
|false||Default. Developers are not excluded from the mailing list.|
This setting specifies where to email reports for errors assigned to "unknown".
|[email]||The reports assigned to t"unknown" are sent to the specified email address.|
|[user]||The reports assigned to t"unknown" are sent to the specified user.|
This setting enables or disables email reports to the manager when an error is found or a fatal exception occurs. Developer emails are not affected by this setting; developer emails are sent only to developers who are responsible for reported errors.
|true||Emails with specific information about errors and fatal exceptions are sent to the manager.|
|false||Default. Emails with specific information about errors and fatal exceptions are not sent to the manager.|
This setting specifies where the Setup Problems section is placed in the report.
|top||The Setup Problems section is placed at the top of the report.|
|bottom||Default. The Setup Problems section is placed at the bottom of the report.|
|hidden||The Setup Problems section is not displayed in the report.|
This setting specifies a limit to the number of messages reported in a single setup problem category.
The maximum number of messages reported in a single setup problem category. The default value is
This setting specifies a limit to the total number of messages displayed in the HTML report in the setup problem section.
The maximum number of the total number of messages reported in the Setup Problem section. The default value is
This setting specifies whether setup problems will be printed on the console.
|true||Default. Setup problems are printed to the console.|
|false||Setup problems are printed to the console.|
This setting specifies how much memory should be used for reports generation.
The maximum amount of memory allocated for report generation. The default is
This setting enables or disables generating reports as a separate virtual machine.
|true||Reports are generated as a separate virtual machine.|
|false||Default. Generating reports as a separate virtual machine is disabled.|
This setting specifies the path to launch file that should be used during reports generation.
The path to the launch file.
This setting specifies how elements in the code duplication findings are sorted.
|oldest||The oldest result is displayed at the top.|
|newests||The newest result is displayed at the top.|
|paths||Default. The results are sorted by full path names in the ascending alphabetical order (A to Z).|
This setting specifies the version of the XML coverage report.
|1||Default. The standard version is used.|
|2||The size of the XML report is optimized.|
This setting determines whether the current installation of the product reports results of local analysis to the DTP server.
The results are published to DTP.
|false||Default. The results are not published to DTP.|
The following configuration enables sending local analysis results to DTP.
This setting specifies whether the tested source code is published to the DTP server.
|off||Source code is not published to DTP. Default when the report.dtp.publish option is enabled.|
|min||The minimal part of the source code is published (in most cases, source code without reference to source control, for example, auto-generated code, is published.|
All of the source code from the specified scope is published to DTP. Default when the report.dtp.publish option is enabled.
The following configuration enables partial publishing of source code to DTP.