In this section:

session.tag

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.

Acceptable Values

Example Usage

The following configuration specifies the ut_linux tag:

session.tag=ut_linux

build.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. 

Acceptable Values

Example Usage

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 abc_project id:

build.id=abc_project

project.module

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.

Acceptable Values

Example Usage

The following configuration specifies the custom XTests module name:

project.module=xTests

exec.env

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. 

Acceptable Values

Example Usage

The following configuration specifies three tags:

exec.env=Windows;x86;gcc_5_4

report.location

This setting specifies the directory where the report will be created.

Acceptable Values

Example Usage

The following configuration specifies the path to the new_reports directory:

report.location=C:\Users\user1\new_reports

report.format

This setting specifies the report format. Use a comma separated list of formats to reports in more than one format.

Acceptable Values

Example Usage

The following configuration specifies the PDF report format:

report.format=pdf

report.custom.extension

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.

Acceptable Values

report.custom.xsl.file

This setting specifies the location of the XSL file for a custom format.

Acceptable Values

report.developer_errors

This setting specifies whether manager reports will include details about developer errors. 

Acceptable Values

Example Usage

The following configuration enables including details about developer errors in the report:

report.developer_errors=true

report.developer_reports

This setting specifies whether the system generates detailed reports for all developers (in addition to the summary report for managers).

Acceptable Values

Example Usage

The following configuration enables generating detailed reports for developers:

report.developer_reports=true

report.authors_details

report.contexts_details

report.suppressed_msgs

report.metadata

report.scontrol

report.associations

issue.tracking.tags

report.assoc.url.[tag]

report.active_rules

report.rules

report.test_params

report.testcases_details

report.coverage.images

report.coverage.limit

report.metrics.attributes

report.archive

report.graph.start_date

report.graph.period

report.mail.enabled

report.mail.server

report.mail.port

report.mail.security

report.mail.subject

report.mail.username
report.mail.password
report.mail.realm

report.mail.domain

report.mail.time_delay

report.mail.from

report.mail.attachments

report.mail.compact

report.mail.format

report.mail.cc

report.mail.include

report.mail.exclude

report.mail.exclude.developers

report.mail.unknown

report.mail.on.error.only

report.setup.problems

report.setup.problems.category_limit

report.setup.problems.display_limit

report.setup.problems.console

report.ue_coverage_details_htmls

report.separate_vm.xmx

report.separate_vm

report.separate_vm.launch.file

dupcode.sorting.mode

report.coverage.version

report.dtp.publish

This setting determines whether the current installation of the product reports results of local analysis to the DTP server.

Acceptable Values

Example Usage

The following configuration enables sending local analysis results to DTP.

report.dtp.publish=true

Related

• Reviewing Results

report.dtp.publish.src

This setting specifies whether the tested source code is published to the DTP server.  

Acceptable Values

Example Usage

The following configuration enables partial publishing of source code to DTP.

report.dtp.publish.src=min

Related

• Reviewing Results