In this section:
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.
The maximum length for a build ID is 128 characters.
| [id] | An id that is used to label results. The default is ${dtp_project}-${time:yyyy-MM-dd}. |
|---|
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: ATM-2017-07-07.
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 BUILD:
build.id=${dtp_project}-${env_var:BUILD}
For the ABC project and the build number 114 on a CI server, this may resolve to ABC-114.
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 a string that describes the environment where the run was executed. It allows you to tag an entire testing session, as well as individual test suites, tests, or test cases via services API. By default, the tag is a combination of the operating system name (e.g., Windows, Linux) and its architecture (e.g., x86, x86_64).
| [tag] | A string that specifies the execution environment details. The default is |
|---|
The following configuration specifies that the run was executed on a 64-bit Linux machine with the GCC 5.4 compiler:
exec.env=linux_x86_64_gcc5.4
This setting specifies the name of a goal–a subset of findings that meet the specified criteria (see goal.severities, goal.projects, goal.max.to.recommend, goal.rules, goal.deadline). The findings are listed in the "Goals" section of the HTML report as recommended for each developer.
You can configure more than one goal by adding a number to the "goal" prefix.
| [goal name] | The name of the goal. |
|---|
The following configuration enables two goals: "Priorities1" and "Priorities2".
goal1.name=Priorities1
goal2.name=Priorities2
This setting specifies the severity level of findings you want to be reported for a goal. This setting requires goal.name to be configured.
You can specify more than one severity.
| [severity level] | A severity level (1-5) or a comma-separated list of severity levels. |
|---|
The following configuration enables the "Priorities1" goal that is a subset of findings with the severity level 1 or 2.
goal1.name=Priorities1
goal1.severities=1,2
This setting specifies the maximum number of findings reported for each developer in the "Goals" section of the HTML report. This setting requires goal.name to be configured.
| [number] | The maximum number of findings reported for each developer. |
|---|
The following configuration specifies a reporting limit for the "Priorities1" goal to be 20.
goal1.name=Priorities1
goal1.severities=1,2
goal1.max.to.recommend=20
This settings specifies that you want a goal to only include findings for a particular project. This setting requires goal.name to be configured.
| [project name] | The name of the project for which the findings are reported. |
|---|
The following configuration specifies that the "Priorities1" goal will only include severity 1 and 2 findings reported for the "examples" project.
goal1.name=Priorities1
goal1.severities=1,2
goal1.projects=examples
This setting specifies the rule(s) that you want to report findings for a goal. This setting requires goal.name to be configured.
| [rule ID] | A rule ID or a comma-separated list of rule IDs. |
|---|
The following configuration specifies that the "Priorities1" goal will only include findings reported for the BD_SECURITY_VPPD and BD_PB_VALRANGE rules.
goal1.name=Priorities1
goal.rules=BD_SECURITY_VPPD,BD_PB_VALRANGE
This setting specifies the deadline for fixing the findings. The number of findings reported for the goal depends on the time left to the deadline: the total number of findings is divided by the number of days left. This setting requires goal.name to be configured.
| [YYY-MM-DD] | The deadline date. |
|---|
The following configuration specifies that all findings reported by the BD_SECURITY_VPPD and BD_PB_VALRANGE rules are to be fixed by May 10, 2019.
goal1.name=Priorities1
goal.rules=BD_SECURITY_VPPD,BD_PB_VALRANGE
goal1.deadline=2019-05-10
This setting specifies the path to a reference report.xml file that will be used as a baseline to identify new findings during the current analysis. Findings detected in the current analysis run are marked as 'new' if they are not present in the reference file specified with this setting.
| [path or URL] | The path or URL to the reference report.xml file. |
|---|
The following configuration specifies that findings detected during the current analysis will be compared against the report.xml file in the 'baseline' directory:
goal.ref.report.file=C:/parasoft/baseline/report.xml
This setting enables or disables excluding existing findings from the report. Existing findings are identified by comparing findings detected in the current analysis run against the reference report.xml file report configured with goal.ref.report.file. If enabled, current findings that are also present in the reference file are excluded from the report.
| true | Only new findings are included in the report. |
|---|---|
| false | Default. New and existing findings are included in the report. |
The following configuration excludes existing findings from the report:
goal.ref.report.file=http://mycompany.com/sa/baseline/report.xml
goal.ref.report.findings.exclude=true
This setting specifies a list of issue tracking tags. It requires the report.associations option to be enabled.
| [tag] | A comma-separated list of tags. The following tags are supported by default: |
|---|
The following configuration disables the default tag asset and enables the custom tag high:
report.associations=true
issue.tracking.tags=fr,pr,req,task,
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:
project.module=xTests
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:
report.active_rules=false
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 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:
report.associations=false
Associating Tests with Development Artifacts
This setting generates a link to an association inside the HTML report. The URL is a query string that contains an [%ID%] placeholder for the PropertyAttribute value. The associated tag must be configured with the issue.tracking.tags option.
| [URL] | The link to the association that will be included in the HTML report. |
|---|
The following configuration enables a custom tag high and generates a link in the HTML report.
report.associations=true
issue.tracking.tags=high
report.assoc.url.high=http://bugzilla.company.com/workitem?id=[%ID%]
Associating Tests with Development Artifacts
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:
report.authors_details=false
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.
report.contexts_details=false
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.
| [tag] | 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.
| [value] | A value that represents the lower coverage limit. The default value is |
|---|
The following configuration sets the lower coverage value to 50:
report.coverage.limit=50
This setting specifies if line hashes are included in the XML coverage report.
| true | Default. Line hashes are included in the coverage report. |
|---|---|
| false | Line hashes are not included in the coverage report. |
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. |
|---|
Use double backslashes to specify the file path on Windows.
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:
report.developer_errors=true
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:
report.developer_reports=true
This setting determines whether the current installation of the product reports results of local analysis to the DTP server.
| true | 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.
report.dtp.publish=true
This setting specifies whether the tested source code is published to the DTP server.
| off | Source code is not published to DTP. |
|---|---|
| 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). |
| full | 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.
report.dtp.publish.src=min
This setting specifies a custom name of the report file.
Note that this setting does not specify the file extension. You can specify the report format using the report.format setting.
|
| [file_name] | The name of the report file. For the default names, see Report File Names. |
|---|
With the following settings configured, the results will be saved in the report-cwe.pdf file.
report.file.name=report-cwe
report.format=pdf
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. |
| sarif | Generates a report in the SARIF format. |
| sarif-azure | Generates a report in the Azure DevOps-specific SARIF format. |
| sate | Generates a report in the SATE format (see https://samate.nist.gov/SATE4.html for details) |
| sast-gitlab | Generates a report in the GitLab-specific SAST format. |
| xunit | Generates a report in the xUnit 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:
report.format=pdf
This setting specifies the start date for trend graphs that track static analysis task, test execution, and coverage. Requires configuring the report.graph.period option.
| [MM/dd/yy] | 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 report.graph.start_date option.
| [?d|?m|?y] | Specifies the duration in the days-months-years format. |
|---|
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 new_reports directory:
report.location=C:\\Users\\user1\\new_reports
This setting enables or disables report emails to developers and additional recipients specified with the report.mail.cc setting.
| 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.
| [host_name] | The host name of the server where the report will be sent. |
|---|
This setting specifies the port for SMTP server.
| [port_number] | 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.
| [subject] | 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.
report.mail.username=user1report.mail.password=Psm#3P!
This setting specifies the mail domain used to send reports.
| [domain] | The domain where the reports are sent. |
|---|
This setting specifies a delay between emailing reports (to avoid bulk email restrictions).
| [time] | 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.
| [email_address] | 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. |
| [email_address] | A list of email addresses separated by semi-colons. |
|---|
This setting specifies email addresses that should be excluded from automatically receiving reports.
| [email_address] | 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 "unknown" are sent to the specified email address. |
|---|---|
| [user] | The reports assigned to "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 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:
report.metadata=false
This setting specifies a list of additional attributes for metric results.
The following attributes are always enabled and don't need to be configured with this setting: module, namespace, type, method.
| [attribute] | A list of comma-separated attributes. |
|---|
This setting specifies a directory for storing static analysis rules HTML files.
| [URL] | The location where the HTML static analysis rule files are stored. |
|---|
Example 1:
report.rules=file:///C:/parasoft/gendoc/
Example 2:
report.rules=../gendoc/
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:
report.scontrol=min
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:
report.suppressed_msgs=true
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.
| [number] | 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.
| [number] | 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.
| [memory_size] | 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.
| [path] | The path to the launch file. |
|---|
Use double backslashes to specify the file path on Windows.
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 specifies a custom parameter Id to be added to the xml report root element. Both report.xml.param{n}.key and report.xml.param{n}.value must be specified for the custom parameter to be added.
| [id] | A unique id of the custom parameter. |
|---|
The following configuration specifies that an attribute with the given key and value will be added to the xml report root element.
report.xml.param1.key=customId
report.xml.param1.value=12345
This setting specifies a custom parameter value to be added to the xml report root element. Both report.xml.param{n}.key and report.xml.param{n}.value must be specified for the custom parameter to be added.
| [value] | A value of the custom parameter. |
|---|
The following configuration specifies that an attribute with the given key and value will be added to the xml report root element.
report.xml.param1.key=customId
report.xml.param1.value=12345
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 ${scontrol_branch}-${exec_env}. |
|---|
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: ${scontrol_branch}-win32_x86_64.
The following configuration specifies a tag other than the default:
session.tag=ut_win