...
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).
Acceptable Values
| [tag name] | A unique tag that identifies results from different sessions. The default is ${scontrol_branch}-${exec_env}. |
|---|
Example Usage
The following configuration specifies the ut_win tag:
session.tag=ut_win
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
buildbuild.id
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.
...
This setting specifies a limit to the number of messages reported in a single setup problem category.
Acceptable Values
...
The maximum number of messages reported in a single setup problem category. The default value is 10.
report.setup.problems.display_limit
This setting specifies a limit to the total number of messages displayed in the HTML report in the setup problem sectionnumber of messages reported in a single setup problem category.
Acceptable Values
| [number] | The maximum number of the total number of messages reported in the Setup Problem sectiona single setup problem category. The default value is |
|---|
report.setup.problems.
...
display_limit
This setting specifies whether setup problems will be printed on the console.
Acceptable Values
...
specifies a limit to the total number of messages displayed in the HTML report in the setup problem section.
Acceptable Values
| [number] | The maximum number of the total number of messages reported in the Setup Problem section. The default value is |
|---|
report.setup.problems.console
This setting specifies whether setup problems will be printed on the console
report.ue_coverage_details_htmls
This setting specifies the type of coverage included in an additional report, which includes source code annotated with line-by-line coverage details when a test's HTML report links to it.
Acceptable Values
| true | Default. Setup problems are printed to the console. |
|---|---|
| false | Setup problems are printed to the console |
| LC | Line coverage is included in the report. |
| DC | Decision coverage is included in the report. |
report.separate_vm.xmx
This setting specifies how much memory should be used for reports generation.
Acceptable Values
| [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.
Acceptable Values
| 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.
Acceptable Values
| [path] | The path to the launch file. |
|---|
...
This setting specifies how elements in the code duplication findings are sorted.
Acceptable Values
| 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.
Acceptable Values
| 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.
Acceptable Values
| true | The results are published to DTP. |
|---|---|
| false | Default. The results are not published to DTP. |
...
This setting specifies whether the tested source code is published to the DTP server.
Acceptable Values
| 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. |
...