In this section:


You can configure how SOAtest connects to other Parasoft systems, reports errors, determines code authorship, and performs other functions by configuring your preferences in a localsettings file. If a parameter is specified in this file and there is an equivalent parameter in the GUI’s Preferences panel (see Configuring SOAtest Across Teams), the localsettings parameter will override the parameter specified from the GUI. Localsettings can be used to:

  • Enter GUI-specified and manually-specified settings into Parasoft DTP, which centralizes reporting and preference distribution across the team.
  • Configure and use different setting configurations for different projects.
  • Extend or override team-wide settings as needed (for example, for settings that involve local paths).
  • Adjust settings without having to open the GUI.
  • Share preferences across a team, as well as to apply different groups of settings to different projects and test runs. 

Defining Localsettings

Localsettings are defined in a .properties configuration file. Enter them manually in a simple text file simple text file. There are no name or location requirements. Each local setting should be entered in a single line.

You can also export your GUI preferences as described in Exporting GUI Preferences to a localsettings File to quickly create the file and adjust or extend them as needed.

Using Variables in Preference Settings

You can use the following variables in your preference configuration settings. The session tag value can not contain any colon characters (:).


This variable specifies the value of an environmental variable. Use a colon followed by the name of a system environment variable before the closing curly brace to output the value of the environment variable.



Outputs the name of the tested project. If more than one project is provided as an input, the name of the project tested is printed followed by an ellipsis (...).



It outputs the name of the general DTP project that results are linked to. Only applies when connected to DTP. 



Outputs the workspace name or Visual Studio solution name.


report.mail.subject=Code Review Scanner Results for ${workspace_name}


Outputs the name of executed test configuration. Only applies to reports and email settings.


report.mail.subject=Findings from running ${config_name} on the ${project_name}


Outputs a comma separated list of enabled analysis types (for example: Static, Execution). Only applies to reports and email settings.


report.mail.subject=${analysis_type} findings


Outputs the name of the tool.


report.mail.subject=Tests executed by ${tool_name}

Specifying Which Localsettings to Use

You can store localsettings in DTP where they are automatically applied to connected tools or in a local file where they can be specified from the command line. 

Multiple layers of localsettings can be active for a single test run.

For details on how to store and apply localsettings, see Configuring SOAtest Across Teams

Additional Notes

  • Each setting should be entered on a single line.
  • If a parameter is specified in localsettings, it will override the related parameter specified from the GUI. If a parameter is not specified in localsettings, the parameter specified in the GUI will be used.
  • If you are importing preferences from localsettings specified in DTP and you want to override these settings from the GUI, you can disable the Use DTP settings option on the appropriate page, then manually configure the settings.
  • If any localsettings problems are detected during a test run, details will be reported in the command line output.
  • If you are running cli mode from a developer/tester desktop (as opposed to from a Server machine), use the tasks.clear=false option to ensure that your results from previous runs are preserved.

Reporting Settings


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



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 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. 
report.graph.ue_coverage_start_date=[MM/dd/yy]Determines the start date for trend graphs that track coverage over a period of time. 
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.

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 team member with assigned tasks will automatically be sent a report that contains only the assigned tasks.  

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

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


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.server=[server]Specifies the mail server used to send reports.
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 "SOAtest Report for Project A", you would use

report.mail.subject=SOAtest 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


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 the Test Suite Summary report section only lists the .tst files (with this option enabled) or displays a tree-like view of the individual tests in each .tst file (with this option disabled). SOAtest only

Default: true


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


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.

Parasoft DTP Settings


Enables auto-configuration using settings stored in DTP.

Default: false


Determines whether SOAtest or Virtualize is connected to DTP. 

Default: false

dtp.user=[username]Specifies the username for DTP user authentication.
dtp.password=[password]Specifies the password for DTP user authentication.
report.dtp.publish=trueEnables/disables publishing test result data to DTP.
dtp.server=[host]Specifies the host name of the Parasoft DTP server. 

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

For more details on general projects, see Connecting to DTP.

Default: Default Project


Specifies the user-defined attributes for Project Center. 

Use the format key1:value1; key2:value2

For more details on attributes, see Connecting to DTP.


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

Default: false


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

Default: true[port]

Specifies the Project Center port.

Default: 32323


Determines whether the current installation is connected to Project Center. 

Default: false

Team Server Settings


Enables/disables the connection to the Parasoft Team Server. 

Default: false[name]Specifies the machine name or IP address of the machine running Team Server. 

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

Licensing Settings

See Manually Adding the License to localsetttings to localsetttings for additional notes and examples.


Determines whether SOAtest retrieves its license from LicenseServer.

Example: soatest.license.use_network=true

Default: true


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


Specifies the LicenseServer port number. 


Default: 2002[edition_name]

Specifies the type of license to retrieve from License Server. 

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


Default: custom_edition


Specifies the maximum number of seconds to wait for the license to be automatically configured from LicenseServer.

Default: 20


Specifies the local license that you want to use.

Default: 0

soatest.license.local.password=[password]Specifies the local password that you want to use. 
soatest.wait.for.tokens.time=[time in minutes]

Specifies how long to wait for a license if a license is not currently available. 



Default: 0

Technical Support Settings


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  

techsupport.archive_location=[directory]Specifies where archives are stored.

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

techsupport.advanced.options=[option]Specifies any advanced options that the support team asked you to enter.

Authorship/Scope Settings


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
#author to email
[email protected]

 Default: team

authors.mapping{n}=[from_user, to_user]

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

For example:


authors.user{n}=[username, email, full_name]

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:


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 how the Recommended Tasks are selected for each team member. You can set the following modes:

random: (default) Assigns a random number tasks.

first: The first tasks reported are shown to each team member per day.


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

scope.xmlmap.file=[file]Specifies the name of the XML file that defines how you want tasks assigned for particular files or sets of files.

Source Control Settings

Defining multiple repositories of the same type

Indexes (numbered from 1 to n) must be added to the prefix if you want to define more than one repository of the same type. For example: 



If you are defining only one repository, you do not need to use an index. For example:


AccuRev Repository Definition Properties

scontrol.rep.type=accurevAccuRev repository type identifier. server host. 
scontrol.rep.accurev.port=AccuRev server port. Default port is 1666.
scontrol.rep.accurev.login=AccuRev user name. 
scontrol.rep.accurev.password=AccuRev password. 

ClearCase Repository Definition Properties

scontrol.ccase.exec=Path to external client executable (cleartool).
scontrol.rep.type=ccaseClearCase repository type name. 
scontrol.rep.ccase.vob= Path inside VOB. ccase.vob value + File.separator  must be the valid path to a ClearCase controlled directory. 

CVS Repository Definition Properties

scontrol.rep.type=cvsCVS repository type identifier. 
scontrol.rep.cvs.root=Full CVSROOT value. 

Plain or encoded password. The encoded password should be the same as in the .cvspass file.

For CVS use the value in .cvspass from within the user's home directory

For CVSNT use the value store in the registry under HKEY_CURRENT_USER\Software\Cvsnt\cvspass

When you are first logged in to the CVS repository from the command line using "cvs login", the password is saved in the registry. To retrieve it, go to the registry (using regedit), and look for the value under HKEY_CURRENT_USER->CVSNT> cvspass. This should display your entire login name (:pserver:exampleA@exampleB:/exampleC) encrypted password value.

scontrol.rep.cvs.useCustomSSHCreden-tials=Determines whether  the cvs login and password should be used for EXT/SSH connections. Allowed values are true and false. It is disabled by default.

If connecting to a CVS server in EXT mode, this specifies which CVS application to start on the server side.

Has the same meaning as the CVS_SERVER variable .cvs is the default value.

scontrol.rep.cvs.ssh.loginname=Specifies the login for SSH connections (if an external program can be used to provide the login).
scontrol.rep.cvs.ssh.password=Specifies the  password for SSH connection.
scontrol.rep.cvs.ssh.keyfile=Specifies the private key file to establish an SSH connection with key authentication.
scontrol.rep.cvs.ssh.passphrase=Specifies the passphrase for SSH connections with the key authentication mechanism.
scontrol.rep.cvs.useShell=Enable an external program (CVS_RSH) to establish a connection to the CVS repository. Allowed values are true and false. It is disabled by default. the path to the executable to be used as the CVS_RSH program. Command line parameters should be specified in the cvs.ext.params property.

Specifies the parameters to be passed to an external program. The following case-sensitive macro definitions can be used to expand values into command line parameters:

  • {host} repository host
  • {port} port
  • {user} cvs user
  • {password} cvs password
  • {extuser} parameter cvs.ssh.loginname
  • {extpassword} parameter cvs.ssh.password
  • {keyfile} parameter cvs.ssh.keyfile
  • {passphrase} parameter cvs.ssh.passphrase

Git Repository Definition Properties

scontrol.rep.type=gitGit repository type identifier.
scontrol.git.exec=Path to Git executable. If not set, assumes git command is on the path.
scontrol.rep.git.branch=The name of the branch that the source control module will use. This can be left blank and the currently checked out branch will be used.
scontrol.rep.git.url=The remote repository URL (e.g., git://hostname/repo.git).
scontrol.rep.git.workspace= The directory containing the local git repository.

Perforce Repository Definition Properties

scontrol.perforce.exec=Path to  external  client executable (p4).
scontrol.rep.type=perforcePerforce repository type identifier. server host. 
scontrol.rep.perforce.port=Perforce server port. Default port is 1666.
scontrol.rep.perforce.login=Perforce user name. 
scontrol.rep.perforce.client=The client workspace name, as specified in the P4CLIENT environment variable or its equivalents. The workspace's root dir should be configured for local path (so that files can be downloaded). 

Serena Dimensions Repository Definition Properties

Linux and Solaris Configuration Note (Eclipse)

To use Serena Dimensions, Linux and Solaris users should run SOAtest in an environment prepared for using Serena programs, such as 'dmcli'

  • LD_LIBRARY_PATH should contain the path to <SERENA Install Dir>/libs.
  • DM_HOME should be specified.

Since many Solaris users commonly set the required Serena variables by running the Serena file, it also necessary to modify LD_LIBRARY_PATH variable. To use Serena Dimensions, LD_LIBRARY_PATH needs to include the following items (paths can be different on client machines):

  • SSL/Crypto library - /usr/local/ssl/lib
  • STDC++ library -  /usr/local/lib
scontrol.rep.type=serenaSerena Dimensions repository type identifier. 
scontrol.serena.dmroot=Path to  the Serena Dimensions executable (e.g., scontrol.serena.dmroot=C\:\\Program Files (x86)\\Serena\\Dimensions 2009 R2\\CM\\)
scontrol.rep.serena.login=Login name.
scontrol.rep.serena.password=Password. Dimensions server host name.
scontrol.rep.serena.dbname=Name of the database for the product you are working with.
scontrol.rep.serena.dbconn=Connection string for that database.
scontrol.rep.serena.locale=The  language used (e.g., scontrol.rep.serena.locale=en_US).

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.

StarTeam Repository Definition Properties

scontrol.rep.type=starteamStarTeam repository type identifier. server host. 
sscontrol.rep.starteam.port=StarTeam server port. Default port is 49201. 
scontrol.rep.starteam.login=Login name. 
scontrol.rep.starteam.password=Password (not encoded).

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




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



Subversion Repository Definition Properties

scontrol.rep.type=svnSubversion repository type identifier. 
scontrol.rep.svn.url=Subversion URL specifies protocol, server name, port and starting repository path (e.g., svn:// 
scontrol.rep.svn.login=Login name. 
scontrol.rep.svn.password =Password (not encoded). 
scontrol.svn.exec=Path to external client executable (svn).

CM Synergy Repository Definition Properties

scontrol.rep.type=synergySynergy/CM repository type identifier. on which synergy/cm engine runs. Local host is used when missing. For Web mode, the  host must be a valid Synergy Web URL with protocol and port (e.g., http://synergy.server:8400).

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

scontrol.rep.synergy.projspec= Synergy project spec which contains project name and its version e.g name-version. 
scontrol.rep.synergy.login=Synergy user name. 
scontrol.rep.synergy.password=Synergy password (not encoded). 
scontrol.rep.synergy.port=Synergy port.
scontrol.rep.synergy.remote_client=(UNIX only) Specifies that you want to start ccm as a remote client. Default value is false. Optional. This is not used for Web mode.
scontrol.rep.synergy.local_dbpath=Specifies the path name to which your data-base information is copied when you are running a remote client session. If null, then the default location will be used. This is not used for Web mode.
scontrol.synergy.exec=Path to external client executable (ccm

Microsoft Team Foundation Server Repository Definition Properties 

scontrol.rep.type=tfsTFS repository type identifier. 
scontrol.rep.tfs.url=TFS repository URL (for example, http://localhost:8080/tfs).
scontrol.rep.tfs.login =TFS user name.
scontrol.rep.tfs.password=TFS password.

Microsoft Visual Source Safe Repository Definition Properties

scontrol.rep.type=vssVisual SourceSafe repository type identifier.
scontrol.rep.vss.ssdir=Path of repository database  (backslash symbols '\' in UNC/Windows paths must be doubled). 
scontrol.rep.vss.projpath=VSS project path. 
scontrol.rep.vss.login=VSS login. 
scontrol.rep.vss.password=VSS password. 
scontrol.vss.exec= Path to external client executable (ss).
scontrol.vss.lookup=Determines whether a full VSS database search is performed to find associations between local paths and repository paths. True or false. 

Important Notes

  • The repository(n).vss.ssdir property shouldco ntain a UNC value even if the repository database resides locally.
  • Be aware of VSS Naming Syntax, Conventions and Limitations. Any character can be used for names or labels, except the following:
    • Dollar sign ($)
    • At sign (@)
    • Angle brackets (< >), brackets ([ ]), braces ({ }), and parentheses (( ))
    • Colon (:) and semicolon (;)
    • Equal sign (=)
    • Caret sign (^)
    • Exclamation point (!)
    • Percent sign (%)
    • Question mark (?)
    • Comma (,)
    • Quotation mark (single or double) (' ")
  • VSS 6.0 (build 8163), which is deployed with Visual Studio 6, does not work properly with projects whose names start with a dot (.) symbol. If such a project name is used, subprojects cannot be added.
  • Do not use custom working directories for sub-projects (example: Project $/SomeProject has the working directory C:\TEMP\VSS\SomeProject and its subproject $/SomeProject/SomeSubProject has the working directory D:\SomeSubProject).

File Encoding Settings


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]<language’s numeric_code>

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

  • JAPANESE = 1
  • CHINESE = 2
  • KOREAN = 5

Miscellaneous Settings


Specifies the directory for rules html files (generated by clicking the Printable Docs button in the Test Configuration’s Static Analysis tab). 

For example:


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.

exec.env=[env1; env2; ...]Specifies a list of tags that describe the environment where a test session was executed. Tags could describe an   operating system (e.g. Windows, Linux), an architecture (e.g. x86, x86_64), a compiler, a browser, etc. These tags describe a complete test session; more environment details could be also added at the test suite, test, or test case levels via the services API.

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: SOAtest controls parallel processing settings.
  • Manual: Allows you to manually configure parallel processing settings to suit your specific needs.
  • Disabled: 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 available memory. 

Default: false

Additional Options for SOAtest and Virtualize


datasources.jdbc.classpath=[path1];[path2];[path3] ...

Specifies the location of JDBC driver jar files and class folders.

Special characters (spaces, slashes, colons, etc.) must be escaped; for instance: 

%20 = SPACE
%3A = :
%5C = \
%7B = {
%7D = }
%24 = $

If listing multiple jars, use \n as a delimiter.

For example, C:\temp\withspace\${example}\jar.jar


C%3A%5Ctemp%5Cwith%20space%5C$2 4%7Bexample%7D%5Cjar.jar\n 

scripting.jython.homeSpecifies the Jython installation directory. This must be a single directory. Use a forward slash (/) or backslash (\) to escape special characters.
scripting.jython.pathUsed to add to your path modules that are not in your jython.home/Lib directory. Multiple paths can be listed. Use a forward slash (/) or backslash (\) to escape special characters.
scripting.timeout.minutesSpecifies the number of minutes after which the product will attempt to stop an unresponsive script and log an error message.[path1];[path2];[path3] ...

Specifies which jar files and class folders are in the classpath. For example:\:\\myjars\\myLib1.jar;C\:\\myjars\\myLib2.jar data models that specify how to convert fixed-length data to and from XML. Enter a semicolon-separated list of directories that contain the appropriate data models.
browsertesting.chrome_executable_pathSpecifies the path to the Chrome executable. 
browsertesting.firefox_executable_path=[path]Specifies the path to the Firefox  executable.
browsertesting.proxy_port=[port]Specifies the proxy port. See the SOAtest User’s Guide> Proxy Configuration Details topic for more information and tips.
browsertesting.browser_communication_port=[port]Specifies the browser communication port.
browsertesting.startup_timeout=[seconds]Specifies the length of delay (in seconds) after which SOAtest should stop waiting for browser startup and consider it to be "timed out."
browsertesting.user_action_timeout=[seconds]Specifies the length of delay (in seconds) after which SOAtest should stop waiting for a user action and consider it to be "timed out."
browsertesting.page_load_timeout=[seconds]Specifies the default length of delay (in seconds) after which SOAtest should stop waiting for a page to load and consider it to be "timed out."


Specifies the default length of delay (in seconds) after which SOAtest should stop waiting for an asynchronous request and consider it to be "timed out."
browsertesting.element_timeout=[seconds]Specifies the default length of delay (in seconds) after which SOAtest should stop waiting for an element and consider it to be "timed out."
browsertesting.dialog_timeout=[seconds]Specifies the default length of delay (in seconds) after which SOAtest should stop waiting for a dialog to open and consider it to be "timed out."

Specifies the default length of delay (in seconds) after which SOAtest should stop waiting for traffic to complete loading and consider it to be
"timed out."

browsertesting.print_debug_info=true|falseDuring recording of a browser functional test scenario, it is possible that an action taken is not recorded by SOAtest. Enabling this option will allow messages to be printed to the console during recording, with information about what events SOAtest handled, any locators that may have been generated, and if applicable, any exceptions that took place during recording.


Allows binary files with the specified extensions to be used in the Traffic Viewer and output. By default, only text files will be allowed. Extension lists are comma-separated.


Allows binary files with the specified MIME types to be used in the Traffic Viewer and output. By default, only text files will be allowed. MIME type lists are comma-separated.
browsertesting.content_fetch_mode=all.con-tent|non.hidden.iframesEnables you to determine whether the contents of hidden frames are dis-played in the pre- and post-action HTML viewer.  For more details on this setting, see the SOAtest User’s Guide. that you want to accept any certificate. This is useful if you want to load pages whose certificates are not "trusted." that you want to accept only certificates from the standard list of Java trusted certificate vendors.

Additional Options for Virtualize Only

Note that options covered in Additional Options for SOAtest and Virtualize also apply to Virtualize.

server.startupDetermines whether the server is automatically started upon Virtualize startup.
server.port.httpSpecifies the port that the Virtualize Server uses for HTTP.
server.port.httpsSpecifies the port that the Virtualize Server uses for HTTPS.
server.port.monitoringSpecifies the port that the Virtualize Server uses for monitoring.

Exclusions are specified in the format: 

traffic.wizard.xpath.ignores=[element name 1]:[value pattern 1];[element name 2]:[value pattern 2];[element name 3]:[value pattern 3]

For example,

traffic.wizard.xpath.ignores=*:[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0- 9]{2}:[0-9]{2}([.][0-9]{1,3})?(([+-][0-9]{2}:[0- 9]{2})|Z)?;uuid:[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}

Note that when the backslash character (\) is used in the regular expression, it needs to be escaped. For example, the regex [\d], which represents a single digit, would be entered as  [\\d].

Additional Options for Continuous Testing Platform (CTP)


Specifies location of the CTP server. Required

Example: env.manager.server=http://em_hostname:8080/

Specifies the name that will be used to label this server in CTP.You can use whatever value will help you identify this server. Optional



Determines whether the Virtualize server notifies CTP when virtual assets are deployed. Optional

Example: env.manager.notify=true


Specifies the username for logging into CTP. Optional

Example: env.manager.username=me


Specifies the password for logging into CTP. Optional

Example: env.manager.password=12345

Sample Localsettings

Example 1

# Team Server settings: (these may be redundant with settings already specified in Team Preferences of the installed version, so may not be needed).
# Report settings
session.tag=<project name>
# Mail settings:
report.mail.enabled=true<[email protected];[email protected]>
report.mail.subject=<Static Analysis results on Project X> 

Example 2

  # Team Server settings
  # Parasoft Project Center settings   
  # Mail settings
  report.mail.subject=Coding Standards   

Example 3

#Determines whether reports are emailed to developers and to the additional recipients specified with the cc setting.
#Remember that if the team is using CVS for source control and each developer's email address matches his or her CVS username + the mail domain, 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.

#Exclude developers emails (true/false) 
# Append developers errors to manager emails (true/false) 
# Send reports to developers (true|false) 
# Append suppressed messages (true|false) 
#Determines where to mail complete test reports.
#This setting is typically used to send reports to managers or architects.
#It can also be used to send reports to developers if developer reports
#are not sent automatically (for example, because the team is not using CVS). 
[email protected]; ${env_var:USERNAME}
# mail target for unknown developer errors 
[email protected]
#Specifies the mail server used to send reports.
#Specifies the mail domain used to send reports.
#Specify mali from 
#Specifies any email addresses you do not want to receive reports.
#This setting is used to prevent from automatically sending reports to someone that worked on the code, but should not be receiving reports. This setting is only applicable if the team is using CVS for source control and developer reports are being sent automatically.
# Specifies the subject line of the emails sent.
report.mail.subject= ${tool_name} Report - ${config_name}
# Report test params include (true|false) 
# Team Server
#Determines whether the current installation is connected to the Team Server. 
#Specifies the machine name or IP address of the machine running Team Server.
#Specifies the Team Server port number. 
session.tag= ${config_name}
# Parasoft Project Center
#Determines the current installation is connected to Project Center. 
#Specifies the host name of the Project Center server.
# Specifies the port number of the Project Center report collector.
# Specifies user-defined attributes for Project Center.
#Use the format key1:value1; key2:value2
#Attributes help you mark results in ways that are meaningful to your organization.
#They also determine how results are grouped in Project Center and how you can filter results in Project Center.
#For example, you might want to label results by project name and/or by project component name. #Each attribute contains two components: a general attribute category name
#and a specific identification value. For example, assume your organization wants to classify results by project.
#You might then use the attribute project:projname1. For the next project, you could use a different
#localsettings file that specified an attribute such as project:projname2.
# Determines whether the results sent to Project Center are marked as being from a nightly build.
#code authorship based on CVS 
#code authorship based on author tag
#code authorship based on local user 
#override license settings
  • No labels