Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



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.

The default is ${dtp_project}-yyyy-MM-dd.


Determines if the reports contain a list of the rules that were enabled for the test.

Default: false


Enables the generation of an additional compressed archive (.zip) file in the specified report location. The ZIP file contains all the files generated to build the report. 

This option can generate an archive for any report format (e.g., HTML, CSV, PDF, etc.). 

By generating an archive, you can also perform custom transformations of the report because all of the elements are generated to the specified destination folder.

Default: false


Specifies whether the report shows requirements, defects, tasks, and feature requests that are associated with a test.

Default: false


Determines whether the report includes an overview of the number and type of tasks assigned to each team member. 

Default: true


Determines whether the report includes an overview of the files that were checked or executed during testing.

Default: false



Specifies the location and extension of the XSL file for a custom format. Used with report.format=custom

For details and examples, see Configuring Reporting Settings.


Determines whether manager reports include details about team member tasks.

Default: false


Determines whether the system generates detailed reports for all team members (in addition to a summary report for managers). 

Default: true


Specifies the report format.

Default: html


Determines whether HTML reports are generated and saved on the local file system. XML reports are generated and saved regardless of this setting’s value.

Default: true

report.graph.cs_start_date=[MM/dd/yy]Determines the start date for trend graphs that track static analysis tasks over a period of time. See Understanding Reports for more details on these reports.
report.graph.ue_coverage_start_date=[MM/dd/yy]Determines the start date for trend graphs that track coverage over a period of time. See Understanding Reports for more details on these reports.
report.graph.ue_start_date=[MM/dd/yy]Determines the start date for trend graphs that track test execution results over a period of time. 

Specifies whether absolute file paths are added to XML data. This needs to be enabled on the Server installation if you want to relocate tasks upon import to desktop installations. 

Default: false


Determines whether reports are sent as attachments. All components are included as attachments; before you can view an HTML report with images, all attachments must be saved to the disk.

Default: false[email_addresses]Specifies where to mail comprehensive manager reports. This setting must be followed by a semicolon-separated list of email addresses. This setting is typically used to send reports to managers or architects. It can also be used to send comprehensive reports to team members if such reports are not sent automatically (for example, because the team is not using a supported source control system).

Specifies that you want to email a compact report or link rather than a complete report. 

If trends is used, the email contains a trend graphs, summary tables, and other compact data; detailed data is not included.

If links is used, the email contains only a link to a report (which is available on Team Server)

report.mail.domain=[domain]Specifies the mail domain used to send reports.

Determines whether reports are emailed to team members  and to the additional recipients specified with the cc setting. 

Remember that each developer that worked on project code will automatically be sent a report that contains only the errors/results related to his or her work.

Default: false

report.mail.exclude=[email_addresses]Specifies any email addresses you do not want to receive reports. This set-ting is used to prevent automated sending of reports to someone that worked on the code, but should not be receiving reports.

Specifies whether reports should be mailed to any team member whose email is not explicitly listed in the property. This setting is used to prevent reports from being mailed to individual developers.

Default: false


Specifies the email format.

Default: html

report.mail.from=[email_address OR user_name_of_the_same_domain]

Specifies the "from" line of the emails sent.

Default: <global_user_name>

report.mail.include=[email_addresses]Specifies the email addresses of team members that you want to receive individual reports. This setting must be followed by a semicolon-separated list of email addresses. This setting is typically used to send individual reports to team members if such reports are not sent automatically (for example, because the team is not using a supported source control system). It overrides team members specified in the 'exclude' list. 

Determines whether reports are sent to the manager only if a task is generated or a fatal exception occurs. Team member emails are not affected by this setting; individual emails are sent only to team members who are responsible for reported tasks.

Default: false

report.mail.server=[server]Specifies the mail server used to send reports.

Specifies the mail server host’s port number.

Default: 25[SL| STARTTLS| NONE]Specifies the desired security. Available settings are  SSL, STARTTLS, NONE. SSL is not available in Visual Studio.
report.mail.subject=My New Subject

Specifies the subject line of the emails sent. The default subject line is ${tool_name} Report - ${config_name}. For example, if you want to change the subject line to "Report for Project A", you would use

report.mail.subject=Report for Project A

Default: ${tool_name} Report - ${config_name}


Specifies a time delay between emailing reports (to avoid bulk email restrictions).

Default: 0

report.mail.unknown=[email_address OR user_name_of_the_same_domain]Specifies where to mail reports for errors assigned to "unknown".
report.mail.username=[username] report.mail.password=[password] report.mail.realm=[realm]

Specifies the settings for SMTP server authentication.

The realm value is required only for those servers that authenticate using SASL realm.


Determines whether an XML report with metrics summary information (as well as individual class and method detail data where applicable) is produced. This report will be generated only when a metrics-enabled Test Configuration is run. Metrics details will be shown in HTML and PDF reports.

Default: true[path]Specifies the path to the location when the reference report file will be created during analysis. See Configuring Task Reporting Preferences.

Determines whether reports include a section about setup problems. 

top - Adds a "Setup Problems" section to the top of the report. This is the default. 

hidden - Prevents a "Setup Problems" section from being added.

bottom - Adds a "Setup Problems" section to the bottom of the report. 

Default: bottom


Determines whether reports include suppressed messages.

Default: false


Determines whether reports include test parameter details.

Default: false


Determines whether a test's HTML report links to another report that includes source code annotated with line-by-line coverage details. 

The following values can be used for [coverage_type]:

LC - for line coverage
SC - for statement coverage
BCC - for block coverage
DC - for decision coverage
SCC - for simple condition coverage
MCDC - for MC/DC coverage


Specifies a session tag used to label these results. This value is used for uploading summary results to Team Server. 

The tag is an identifier of the module checked during the analysis process. Reports for different modules should be marked with different tags.

Default: ${config_name}

This setting specifies if additional information from source control, such as revisions and comments, is included in the report.