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. 

Default: build-yyyy-MM-dd HH:mm:ss

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

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 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)

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

Remember that each team member with assigned tasks will automatically be sent a report that contains only the assigned tasks.  

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 team members.

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

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}

tasks.source.control.details=true|false

Enables autoconfiguration with Parasoft Test settings stored on the DTP server.

Default: false

Determines whether the current C++testt is connected to DTP. 

Default: false

Determines whether C/C++test is connected to Parasoft Project Center. 

Default: false

Specifies the Parasoft Project Center port.

Default: 32323

Specifies the Parasoft DTP server port.

Default: 80

Specifies the user-defined attributes for Parasoft Project Center. 

Use the format key1:value1; key2:value2

For more details on attributes, see Connecting to Project Center.

Determines whether the results sent to Parasoft Project Center are marked as being from a nightly build. 

Default: false

Determines whether Parasoft Project Center attributes specified in the GUI at the project level should be used. This allows you to disable project-level Parasoft Project Center attributes.

Default: true

Specifies the name of the DTP project that you want these results linked to. 

For more details on general projects, see Connecting to Project Center.

Default: Default Project

Determines whether C/C++test is connected to the Parasoft Team Server. 

Default: false

Specifies the Team Server port number.

Default: 18888

Determines whether username and password are submitted to connect to Team Server. Usernames/passwords are not always needed; it depends on your team’s setup. 

If the first setting is true, the second and third settings specify the username and password.

Note that Team Server must have the username and password setting already enabled before these settings can be used.

tcm.server.accountLogin default: false

Determines whether C/C++test retrieves its license from LicenseServer.

Example: cpptest.license.use_network=true

Default: true

Specifies the machine name or IP address of the machine running License Server Configuration Manager. 

Example: cpptest.license.network.host=10.9.1.63

Specifies the License Server port number. 

Example: cpptest.license.network.port=2222

Default: 2002

cpptest.license.
network.edition=[edition_name]

Specifies the type of license that you want C/C++test to retrieve from License Server. 

[edition_name] can be automation_edition. To use a custom edition, do not set anything after the "="; simply leaving the value empty.

Example:

cpptest.license.network.edition=desktop_edition

cpptest.license.network.edition=automation_edition

Default: custom_edition

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

Default: 20

cpptest.license.
local.expiration=[expiration]

Specifies the local license that you want C/C++test to use.

Default: 0

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.wait.for.tokens.time=3.

Default: 0

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 where the authorship mapping file is stored. This setting defaults to team unless local or shared is specified.

If set to local (recommended), authorship mappings can be set directly in localsettings. See authors.mapping and authors.user{n} for details.

If set to shared, you can store map-pings in a local file using the authors.mappings.file option. 

The team and shared options are deprecated. Files specified by these options should be in the previously-used format of:

#author to author
user1=user3
user2=user3
#author to email
[email protected]

 Default: team

Specifies a specific author mapping for authors.mappings.location=local, as described above.

For example:

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

Specifies a specific author name and email for authors.mappings.location=local.

For example:

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

Specifies the location of a "shared" file as described in authors.mappings.location above.

For example:

authors.mappings.file=/home/user/dev/temp/author_mapping1.txt

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 code authorship is computed  based on a data from a supported source control system. 

Default: false

Determines whether code authorship is computed based on the local user.

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

If the project has been downloaded/moved to a location other than default work area, use this option to specify a mapping between the project (or stream) with the Serena repository and the local project.

If you are working in the default work area, you do not need to define mappings.

When working with large multi-project repositories, you can improve performance by specifying the project, view, or folder that you are currently working with. 

You can indicate  either a simple Project name (all views will be scanned when searching for the repository path), a Project/View (only the given view will scanned) or Project/View/Folder (only the specified Star Team folder will be scanned).

Examples:

scontrol.rep.starteam.path=proj1
scontrol.rep.starteam.path=proj1/view1
scontrol.rep.starteam.path=proj1/view1/folderA
scontrol.rep.starteam.path=proj1/view1/folderA/folderB 

If the scontrol.rep.starteam.path setting specifies a StarTeam view or folder, you can use this field to indicate a new working directory for the selected view's root folder (if the path represents a view) or a new working directory for the selected folder (if the path represents a folder).

Examples:

scontrol.rep.starteam.workdir=c:\\storage\\dv
scontrol.rep.starteam.workdir=/home/storage/dv 

Absolute synergy database path e.g \\host\db\name (backslash symbols '\' in UNC/Windows paths must be doubled).

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 directory for rules html files (generated by clicking the Printable Docs button in the Test Configuration’s Static Analysis tab). 

For example:

report.rules=file:///C:/Temp/Burt/parasoft/xtest/gendoc/report.rules=../gendoc/ 

Default: none

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

Default: true

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

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 Indicating Code and Test Correlations.

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

You can specify an external location, or use the keyword WORKSPACE. If WORKSPACE is used, projects will be created in subdirectories within the workspace directory. 

If BDF_LOC is used and one project will be created, then it will be created in the exact location as the bdf file. If more then one project will be created, then the projects will be created in subdirectories within the bdf file location. Those subdirectories will be named with corresponding projects names.

If an external path is specified, then the project will be created in the specified location.

WORKSPACE is the default.

bdf.import.pathvar.enabled=[true|false]

Specifies what compiler family will be used (for example, vc_6_0, vc_7_0, vc_7_1, vc_8_0, gcc_2_9, gcc_3_2, gcc_3_3, gcc_3_4, ghs_4_0). For a custom compiler, you need to use the custom compiler family identifier, which is the name of the directory containing gui.properties, c.psrc and cpp.psrc files). If this property is not specified, the default values will be used.

Specifies the location of the imported projects. 

If WORKSPACE is used, then the project will be created in workspace. 

If ORIG is used, then the project will be created in the .gpj project location.

If an external path is specified, then the project will be created in the specified location.

The default value is  WORKSPACE.

Specifies whether the .gpj project source folders are linked into the created Eclipse project. 

The default value is  true.

Applicable when gpj.import.location=<path>

Specifies whether the project(s) are  imported into subdirectories or directly into the specified location. 

If you want the project(s) imported into subdirectories created in the specified external location, use true.

If you are importing only one project and you want it imported directly into the specified external location, use false.

The default value is  true (subfolders are created for each project imported into in external location).

Specifies if  path variables should be used when creating linked directories (if the above option is set to true).  

The default value is false.

Specifies the path variable name. The default value will be used unless you specify a path variable name that points to a different location (for instance, DEVEL_ROOT_DIR). 

If a project with the specified name is already defined in the Eclipse workspace and it points to a different location than the value passed in the gpj.import.pathvar.location property, then Path Variable will not be used; full paths will be used instead. Also the default value of gpjimport.pathvar.name will always be DEVEL_ROOT_DIR if the gpjimport.pathvar.name property is not specified. If this property is specified with some <name>, then that <name> will be used as the Path Variable name.

The default value is  DEVEL_ROOT_DIR.

Specifies the location of the imported projects. 

If WORKSPACE is used, then the project will be created in workspace. 

If DSP_LOC is used, then the project will be created in the .dsp project location.

If an external path is specified, then the project will be created in the specified location.

The default value is  WORKSPACE.

Specifies whether the .dsp project source folders are linked into the created Eclipse project. 

The default value is  true.

Applicable when dsp.import.location=<path>

Specifies whether the project(s) are  imported into subdirectories or directly into the specified location. 

If you want the project(s) imported into subdirectories created in the specified external location, use true.

If you are importing only one project and you want it imported directly into the specified external location, use false.

The default value is  true (subfolders are created for each project imported into in external location).

Specifies if  path variables should be used when creating linked directories (if the above option is set to true).  

The default value is false.

Specifies the path variable name. The default value will be used unless you specify a path variable name that points to a different location (for instance, DEVEL_ROOT_DIR). 

If a project with the specified name is already defined in the Eclipse work-space and it points to a different location than the value passed in the dsp.import.pathvar.location property, then Path Variable will not be used; full paths will be used instead. Also the default value of dsp.import.pathvar.name will always be  DEVEL_ROOT_DIR if the dsp.import.pathvar.name property is not specified. If this property is specified with some <name>, then that <name> will be used as the Path Variable name.

The default value is  DEVEL_ROOT_DIR.

Specifies what location the path variable points to. By default, the automatically-generated location will be used. This location is the common root location for all linked directories. If it is not possible to find a common location (for example because .dsp projects are on multiple drives) or the specified location cannot be used,  then the path variable will not be used. Full paths will be used instead.

For example, assume you have the following paths:

path1: c:\a\b\c\proj1
path2: c:\a\b\proj2

The common root location would be c:\a\b

The default value is  automatically-generated.

Specifies which .dsp project configuration should be used. If the specified configuration cannot be found in the imported project, then the  default configuration will be used. 

The configuration name can be passed in two ways: <project_name> - <configuration_name> or only <configuration_name>. If more then one project is imported, then only <configuration_name> should be entered. This prompts the wizard to search for that configuration in all projects.

The default value is the default from .dsp.

Specifies the location of the imported projects.

If WORKSPACE is used, then the project will be created in workspace.

If ORIG is used, then the project will be created in the original project file location.

If an external path is specified, then the project will be created in the specified location.

The default value is WORKSPACE.

Specifies whether the uVision project source folders are linked into the created Eclipse project.

The default value is true.

Applicable when uv.import.location=<path> 

Specifies whether the project(s) are imported into subdirectories or directly into the specified location.

If you want the project(s) imported into subdirectories created in the specified external location, use true.

If you are importing only one project and you want it imported directly into the specified external location, use false.

The default value is true (subfolders are created for each project imported into in external location).

Specifies if path variables should be used when creating linked directories (if the above option is set to true).

The default value is false.

Specifies the path variable name. The default value will be used unless you specify a path variable name that points to a different location (for instance, DEVEL_ROOT_DIR).

If a project with the specified name is already defined in the Eclipse workspace and it points to a different location than the value passed in the uv.import.pathvar.location property, then Path Variable will not be used; full paths will be used instead. Also, the default value of uv.import.pathvar.name will always be DEVEL_ROOT_DIR if the uv.import.pathvar.name property is not specified. If this property is specified with a <name>, then that <name> will be used as the Path Variable name.

The default value is DEVEL_ROOT_DIR.

Specifies the location of the imported projects.

If WORKSPACE is used, then the project will be created in workspace.

If ORIG is used, then the project will be created in the original project file location.

If an external path is specified, then the project will be created in the specified location.

The default value is WORKSPACE.

Specifies whether the HEW project source folders are linked into the created Eclipse project.

The default value is true.

Applicable when hew.import.location=<path>

Specifies whether the project(s) are imported into subdirectories or directly into the specified location.

If you want the project(s) imported into subdirectories created in the specified external location, use true.

If you are importing only one project and you want it imported directly into the specified external location, use false.

The default value is true (subfolders are created for each project imported into in external location).

Specifies if path variables should be used when creating linked directories (if the above option is set to true).

The default value is false.

Specifies the path variable name. The default value will be used unless you specify a path variable name that points to a different location (for instance, DEVEL_ROOT_DIR).

If a project with the specified name is already defined in the Eclipse workspace and it points to a different location than the value passed in the hew.import.pathvar.location property, then Path Variable will not be used; full paths will be used instead. Also the default value of hew.import.pathvar.name will always be DEVEL_ROOT_DIR if the hew.import.pathvar.name property is not specified. If this property is specified with a <name>, then that <name> will be used as the Path Variable name.

The default value is DEVEL_ROOT_DIR.