...
The following configuration enables including information about repositories, file paths, and revisions in the report:
report.scontrol=min
| Anchor | ||||
|---|---|---|---|---|
|
This setting enables or disables showing requirements, defects, tasks, and feature requests associated with a test in the report.
...
report.associations=false
| Anchor | ||||
|---|---|---|---|---|
|
This setting specifies a list of issue tracking tags. It requires the report.associations option to be enabled.
Acceptable Values
| [tag] | A comma-separated list of tags. The following tags are supported by default: |
|---|
Example Usage
The following confiuration disables the default tag asset and enables the custom tags high and test:
report.associations=true
issue.tracking.tags=fr,pr,high,testreq,task,
report.assoc.url.[tag]
This setting generates a link to an association inside the HTML report. The URL is a query string containing that contains an [%ID%] placeholder for the PropertyAttribute value. The associated tag must be configured with the issue.tracking.tags option.
Acceptable Values
| [URL] | The link to the association that will be included in the HTML report. |
|---|
Example Usage
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%]
report.active_rules
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. |
Example Usage
The following configuration disables showing the rules that were enabled during analysis in the report:
...
| [URL] | The location where the HTML static analysis rule files are stored. |
|---|
Example Usage
Example 1:
report.rules=file:///C:/parasoft/gendoc/
...
| true | Google Test assertion failures are included in the report. |
|---|---|
| false | Google Test assertion failures are not included in the report. |
Example Usage
The following configuration enables showing Google Test Assertion failures:
...
| [value] | A value that represents the lower coverage limit. The default value is |
|---|
Example Usage
The following configuration sets the lower coverage value to 50:
...
| [email_address] | A list of email addresses separated by semi-colons. |
|---|
Example Usage
[email protected];[email protected]
...
| true | The results are published to DTP. |
|---|---|
| false | Default. The results are not published to DTP. |
Example Usage
The following configuration enables sending local analysis results to DTP.
...
| 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). |
| full | All of the source code from the specified scope is published to DTP. Default when the report.dtp.publish option is enabled. |
Example Usage
The following configuration enables partial publishing of source code to DTP.
...
| [goal name] | The name of the goal. |
|---|
Example Usage
The following configuration enables two goals: "Priorities1" and "Priorities2".
...
| [severity level] | A severity level (1-5) or a comma-separated list of severity levels. |
|---|
Example Usage
The following configuration enables the "Priorities1" goal that is a subset of findings with the severity level 1 or 2.
...
| [number] | The maximum number of findings reported for each developer. |
|---|
Example Usage
The following configuration specifies a reporting limit for the "Priorities1" goal to be 20.
...
| [project name] | The name of the project for which the findings are reported. |
|---|
Example Usage
The following configuration specifies that the "Priorities1" goal will only include severity 1 and 2 findings reported for the "examples" project.
...
| [rule ID] | A rule ID or a comma-separated list of rule IDs. |
|---|
Example Usage
The following configuration specifies that the "Priorities1" goal will only include findings reported for the BD_SECURITY_VPPD and BD_PB_VALRANGE rules.
...
| [YYY-MM-DD] | The deadline date. |
|---|
Example Usage
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.
...