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}-${time:yyyy-MM-dd}. 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.

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

report.custom.extension

report.custom.xsl.file

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

For details and examples, see Configuring Report 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 whether the tested source code is published to the DTP server.  

If set to off, the source code is not published to DTP.

If set to 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).

If set to full, all of the source code from the specified scope is published to DTP.

Default: full (Default when the report.dtp.publish option is enabled.)

report.format=html|pdf|sarif|sarif-azure|

sast-gitlab|sate|xunit|custom

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

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

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

If trends is used, the email contains 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 DTP server).

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

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

Default: false

Specifies the email format.

Default: html

Specifies the "from" line of the emails sent.

Default: <global_user_name>

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

Specifies the mail server host’s port number.

Default: 25

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

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

This setting specifies a path to the directory containing static analysis rules HTML files. Based on that path, links to rule documentation are added in HTML reports. 
The rules HTML files are provided by tools or can be generated by clicking the Printable Docs button in the Static tab of the Test Configuration.

To apply this setting in the GUI, you need to define it in a .properties file and then provide a path to this file in the Option file field in the Report & Publish window. For more details, see Generating Reports.

For example:

report.rules=file:///C:/Temp/Burt/parasoft/xtest/gendoc/
report.rules=../gendoc/
report.rules=file:///<TOOL_INSTALL>/rules/docs/

Default: none

Specifies if and how much additional information from source control is included in the report.

If set to off, information from source control is not included in the report.

If set to min, the report includes information about repositories, file paths, and revisions.

If set to full, the report includes information about repositories, file paths, and revisions, as well as task revisions and comments.

Default: off

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

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}

tasks.source.control.details=true|false

Allows you to accept the terms of Parasoft End User License Agreement (EULA).

Default: false

Enables or disables retrieving a network license.

Example: cpptest.license.use_network=true

Default: true

By default, C/C++test will try to retrieve a license form License Server on the DTP configured as your primary DTP server; see Parasoft DTP Settings. If you want to configure another License Server, enable the license.network.use.specified.server option.

Specifies the expiration date of the local license.

Default: 0

Specifies the type of the network license that will be retrieved from DTP or Licence Server. This setting requires that the cpptest.license.use_network is set to true.

Acceptable edition names:

• desktop_edition: The license is optimized for desktop usage.
• desktop_compliance_edition: The license is optimized for desktop usage and configured to support compliance with coding standards.
• automation_edition: The license is configured for high-performance usage in server command line mode.
• automation_compliance_edition: The license is configured for high-performance usage in server command line mode and includes support for compliance with coding standards.
• custom_edition: The customized license that requires specifying the list of available features. Use cpptest.license.custom_edition_features to specify the list of features.

Default: custom_edition

Example:

The following configuration enables the license optimized for desktop usage.
cpptest.license.use_network=true
cpptest.license.network.edition=deskop_edition

Specifies the features you want to enable in the custom edition of the C/C++test license. You can use a comma-separated list to specify more than one feature.

Acceptable feature names:

• Assembly Coverage
• Automation
• AUTOSAR Rules
• Code Dependency Export
• Static Analysis
• Coverage
• Coverage Advisor
• CWE Rules
• Desktop Command Line
• DISA STIG Rules
• DTP Publish
• Embedded Support
• Flow Analysis
• HIC++ Rules
• JSF Rules
• MISRA C 2012 Rules
• MISRA Rules
• OWASP Rules
• Requirements Traceability
• Rule Wizard
• Runtime Error Detection
• Security Rules
• SEI CERT C Rules
• SEI CERT C++ Rules
• Unit Test

Specifies the time that C/C++test will wait for a license if a license is not currently available. 

For example to make C++test  wait 3 minutes for license tokens, use cpptest.license.wait.for.tokens.time=3.

Default: 0

Specifies the maximum number of seconds C/C++test will  wait for the license to be automatically configured from License Server.

Default: 20

Enables or disables retrieving the license from a custom License Server specified with the license.network.url option.

Example: license.network.use.specified.server=true

Default: false

Specifies the the URL to the standalone License Server or secondary DTP that you use to obtain the license. It requires the license.network.use.specified.server option set to true.

The default port numbers are:

• For a standalone License Server: 8080
• For a License Server on secondary DTP:  
  • 8443 for https://
  • 8080 (on Linux) and 80 (on Windows) for http://

If DTP is deployed to a location other than the root of the host server, the URL should include a context path (a relative path from the host name). This may be the case if your organization uses a reverse proxy. The context path is not supported for a standalone License Server. Refer to the DTP documentation for additional information about reverse proxy server configuration and context path configuration. 

Example: license.network.url=http://jade.mycompany.com:8080

Example including a context path: license.network.url=https://aurelia.mycompany.com:8443/contextPath

Enables or disables authentication on the secondary DTP server specified with the license.network.url option.

It requires the license.network.use.specified.server option to be set to true.

Specifies the username for authentication on the secondary DTP server specified with the license.network.url option. It requires the license.network.use.specified.server and license.network.auth.enabled options set to true.

Example: license.network.user=JohnSnow

Specifies the password for authentication on the secondary DTP server specified with the license.network.url option. It requires the license.network.use.specified.server and license.network.auth.enabled options set to true, and the the license.network.user to be configured. We highly recommend that you use an encoded password to ensure successful authentication and increase the level of security; see Creating an Encoded Password.

Example: license.network.password=Wic2019!

Determines whether archives are automatically prepared when testing problems occur.

Default: false

Determines whether prepared archives are emailed to Parasoft support. If you enable this, be sure to specify email settings from the GUI or with the options in Reporting Settings.

Default: false  

Determines whether verbose logs are included in the archive. Note that this option cannot be enabled if the logging system has custom configurations.

• Verbose logs are stored in the xtest.log file within the user-home temporary location (on Windows, this is <drive>:\Documents and Settings\<user>\Local Settings\Temp\parasoft\xtest).

• Verbose logging state is cross-session persistent (restored on application startup).

• The log file is a rolling file: it won't grow over a certain size, and each time it achieves the maximum size, a backup will be created.

Default: false

Determines whether verbose logs include output from source control commands. Note that the output could include fragments of your source code.  

Default: false

Determines whether general application logs are included.

Default: false

Determines whether environment variables, JVM system properties, platform details, additional properties (memory, other) are included in the archive.

Default: false

Specifies if advanced options will be sent.

Default: false

Specifies any advanced options that the support team asked you to enter.

Default: false

Specifies if additional data generated during analysis will be sent.

Default: false

Specifies a specific author mapping.

For example:

authors.mapping1=baduser,gooduser
authors.mapping2=brokenuser,fixeduser 
authors.mapping3=olduser,newuser 

Specifies a specific author name and email.

For example:

authors.user1=dan,[email protected],Dan Stowe
authors.user2=jim,[email protected],Jim White 

Determines whether author names are case sensitive. If true, David and david will be considered the same user. If false, David and david will be considered two separate users.

Default: false

Determines whether C++test computes code authorship based on a data from a supported source control system. This setting is not needed if you want to use the value specified in the GUI.

Default: false

Determines whether C++test computes code authorship based on the local user. This setting is not needed if you want to use the value specified in the GUI.

Default: true

Determines whether task assignment is computed based on XML files that define how you want tasks assigned for particular files or sets of files (these mappings can be specified in the GUI then saved in an XML file).

Default: true

Defines how file encoding is calculated. 

default specifies that you want to use system properties.

user indicates that you will explicitly specify the encoding name (using the setting below).

auto enables automatic detection of encoding for the Far-East language specified with fileencoding.autolanguage.

Default: default

If fileencoding.mode is set to user, this specifies the encoding name 

Valid names are ASCII-US, UTF-8, UTF-16, UTF-16LE, UTF-16BE or java.nio canonical name. 

It should be specified in form parasoft-dotNET-[codepagenumber]

If fileencoding.mode is set to auto, this specifies the language’s numeric code. Valid codes are:

• JAPANESE = 1
• CHINESE = 2
• SIMPLIFIED CHINESE = 3
• TRADITIONAL CHINESE = 4
• KOREAN = 5

Specifies the verbosity level for the Console view. Available settings are:

low: Configures the Console view to show errors and basic information about the current step’s name and status (done, failed, up-to-date).

normal: Also shows command lines and issues reported during test and analysis.

high: Also shows warnings.

Default: low

Clears existing tasks upon startup in cli mode. This prevents excessive time being spent "loading existing results." 

Default: true

Indicates where user-defined rules are saved.

Indicates where user-defined Test Configurations are saved.

Specifies custom issue tracking tags. Multiple tags can be separated by a comma. For example:

issue.tracking.tags=@custom,@pr ,@fr

For more details, see Associating Tests with Development Artifacts.

Determines which of the following modes is active: 

• Auto: Allows C/C++test to control parallel processing settings.
• Manual: Allows you to manually configure parallel processing settings to suit your specific needs.
• Disabled: Configures C/C++test to use only one of the available CPUs.

For more details on this and other parallel processing options, see Configuring Parallel Processing.

Default: Auto

Specifies the maximum number of  parallel threads that can be executed simultaneously.  The actual number of parallel threads is determined based on the number of CPUs, available memory, and license settings.

Default: [available_processors]

Specifies the amount of memory that should be kept free in low memory conditions (expressed as a percentage of the total memory available for the application). This is used to ensure that free memory is available for other processes.

Default: 25

Indicates that you do not want to place any restrictions (beyond existing system limitations) on the memory available to Parasoft Test. 

Default: false

Enables or disables returning the 0x40 exit code, which indicates that setup problems were reported when the process failed; see Command Line Exit Codes for details.

Default: false

Enables or disables collecting anonymous usage information and sending it to Parasoft. Read our privacy statement to learn more at https://www.parasoft.com/privacy-policy.

Default: false