In this section:
Overview
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 settings 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 settings parameter will override the parameter specified from the GUI. Settings can be imported into the GUI from the command line as well; see "-settings" or "-property" on the CLI Options page for more information about that process.
Settings 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 Settings
Settings are defined in a .properties configuration file. Enter them manually in a simple text file. There are no name or location requirements. Each setting should be entered in a single line.
You can also export your GUI preferences as described in Exporting GUI Preferences to a settings 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 cannot contain any colon characters (:).
env_var | 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. Example:
|
---|---|
project_name | 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 (...). Example:
|
general_project | Outputs the name of the general DTP project to which results are linked. Only applies when connected to DTP. Example:
|
workspace_name | Outputs the workspace name or Visual Studio solution name. Example:
|
config_name | Outputs the name of executed test configuration. Only applies to reports and email settings. Example:
|
analysis_type | Outputs a comma-separated list of enabled analysis types (for example: Static, Execution). Only applies to reports and email settings. Example:
|
tool_name | Outputs the name of the tool. Example:
|
time | Outputs the current time. The default is
|
Specifying Which Settings to Use
You can store settings 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 settings can be active for a single test run.
For details on how to store and apply settings, see Configuring SOAtest Across Teams.
Additional Notes
- Each setting should be entered on a single line.
- If a parameter is specified in settings, it will override the related parameter specified from the GUI. If a parameter is not specified in settings, the parameter specified in the GUI will be used.
- If you are importing preferences from settings 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 settings 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
Setting | Purpose |
---|---|
build.id | 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. Default: |
report.active_rules=true|false | Determines if the reports contain a list of the rules that were enabled for the test. Default: |
report.archive=true|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 (for example, HTML, CSV, PDF, and so forth). 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: |
report.associations=true|false | Specifies whether the report shows requirements, defects, tasks, and feature requests that are associated with a test. Default: |
report.authors_details=true|false | Determines whether the report includes an overview of the number and type of tasks assigned to each team member. Default: |
report.contexts_details=true|false | Determines whether the report includes an overview of the files that were checked or executed during testing. Default: |
report.coverage.version=1|2 | Specifies the version of the XML coverage report. Acceptable values are:
Default is |
| Specifies the location and extension of the XSL file for a custom format. Used with For details and examples, see Configuring Report Settings. |
report.developer_errors=true|false | Determines whether manager reports include details about team member tasks. Default: |
report.developer_reports=true|false | Determines whether the system generates detailed reports for all team members (in addition to a summary report for managers). Default: |
report.format=html|pdf|sate|xunit|custom | Specifies the report format. Available formats are HTML, PDF, SATE, XUnit, and custom. Default: |
report.generate_htmls=true|false | 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: |
report.mail.attachments=true|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: |
report.mail.cc=[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. |
report.mail.compact=trends|links | Specifies that you want to email a compact report or link rather than a complete report. If If |
report.mail.domain=[domain] | Specifies the mail domain used to send reports. |
report.mail.enabled=true|false | Determines whether reports are emailed to team members and to the additional recipients specified with the Remember that each team member with assigned tasks will automatically be sent a report that contains only the assigned tasks. Default: |
report.mail.exclude=[email_addresses] | Specifies any email addresses you do not want to receive reports. This setting is used to prevent automated sending of reports to someone that worked on the code but should not be receiving reports. |
report.mail.exclude.developers=true|false | Specifies whether reports should be mailed to any team member whose email is not explicitly listed in the Default: |
report.mail.format=html|ascii | Specifies the email format. Available formats are HTML and ASCII. Default: |
report.mail.from=[email_address OR user_name_of_the_same_domain] | Specifies the "from" line of the emails sent. Default: |
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. |
report.mail.on.error.only=true|false | 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: |
report.mail.port=[port] | Specifies the mail server host’s port number. Default: |
report.mail.security=[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
Default: |
report.mail.time_delay=[server] | Specifies a time delay between emailing reports (to avoid bulk email restrictions). Default: |
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 |
report.metrics_details=true|false | 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: |
report.organize_security_findings_by=CWE|OWASP2021 | Specifies whether API Security reports are sorted by CWE or OWASP 2021 Top 10. Default: |
report.rules=[url_path_to_rules_directory] | 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. 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:
Default: none |
report.setup.problems=top|bottom|hidden | Determines whether reports include a section about setup problems.
Default: |
report.suppressed_msgs=true|false | Determines whether reports include suppressed messages. Default: |
report.test_params=true|false | Determines whether reports include test parameter details. Default: |
report.test_suites_only=true|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: |
report.ue_coverage_details_htmls=[coverage_type] | 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 |
session.tag=[name] | Specifies a session tag used to label these results. The tag is an identifier of the module checked during the analysis process. Reports for different modules should be marked with different tags. Default: |
| This setting specifies if additional information from source control, such as revisions and comments, is included in the report. |
DTP Settings
Setting | Purpose |
---|---|
dtp.autoconfig=true|false | Enables auto-configuration using settings stored in DTP. This setting does not apply to the GUI and is ignored during import (see "-settings" or "-property" on the CLI Options page for more information about that process). Default: |
dtp.enabled=true|false | Determines whether SOAtest or Virtualize is connected to DTP. Default: |
dtp.url=[url] | Specifies the URL for the DTP server. Include the protocol and host name or IP address and, if appropriate, the port number and context path. |
dtp.user=[username] | Specifies the username for DTP user authentication. |
dtp.password=[password] | Specifies the password for DTP user authentication. We strongly recommend encoding your password to ensure successful authentication and a secure connection. You can encode your password by running a command line instance of SOAtest with the See CLI Options for additional information. |
report.dtp.publish=true | Enables/disables publishing test result data to DTP. |
dtp.project=[project_name] | Specifies the name of the DTP project to which you want these results linked. For more details on general projects, see Connecting to DTP. Default: Default Project |
Application Coverage Settings
Setting | Purpose |
---|---|
application.coverage.enabled=true|false | Specifies whether application coverage is enabled or not. Default: |
application.coverage.agent.url=[url] | Specifies URLs where the applications under test and coverage agents are hosted. Include the protocol (HTTP/HTTPS) and port. Separate multiple entries with a semi-colon ( ; ). Example: |
application.coverage.user.id=[username] | Specifies a user ID so that coverage results can be associated with a specific user. A user ID should only be specified when the coverage agent is configured to run in multi-user mode. See the DTP Engine documentation for details. |
application.coverage.dtp.publish=true|false | Specifies whether coverage reports should be uploaded to DTP. If you have configured multiple coverage agents, their coverage reports will be merged into a single coverage report for DTP. Defaults to the value of |
application.coverage.binaries=[file|URL] | Specifies the URL or local file that contains binaries of the application under test (AUT). You can specify the path to a folder or a .war, .jar, .zip, or .ear file. Optional. Not needed if the static coverage file is uploaded to DTP separately. Do not use if application.coverage.static.file has been specified. |
application.coverage.binaries.exclude=[pattern] | Specifies a comma-separated pattern of binaries to exclude during AUT scanning. Optional. Analysis of binaries will take longer and analyze more of the application than needed if not used. Do not use if
Example: |
application.coverage.binaries.include=[pattern] | Specifies a comma-separated pattern of binaries to include during AUT scanning. Optional. Analysis of binaries will take longer and analyze more of the application than needed if not used. Do not use if
Example: |
application.coverage.static.file=[file|URL] | Specifies the URL or local file of the static coverage file generated with dotTEST or Jtest in the .xml or .data format. Optional. Not needed if the static coverage file is uploaded to DTP separately. Do not use if See Creating a Custom Test Configuration for more information. Example: |
application.coverage.images=$[dtp_project] | Specifies a set of tags that are used to create coverage images in DTP. A coverage image is a unique identifier for aggregating coverage data from runs with the same build ID. Separate multiple entries with a semi-colon ( ; ). For details, see the Parasoft DTP user guide. Example: |
application.coverage.runtime.dir=[directory] | Specifies a directory to which to save a copy of the runtime coverage data. If no directory is specified, runtime coverage data is not saved after processing. Optional. |
application.coverage.test.associations=true|false | Enables the storing of test associations with runtime coverage data. If set to Default: |
Licensing Settings
Setting | Purpose |
---|---|
soatest.license.use_network=true|false | Enables/disables network-based licenses. Set to Set to Example: Default: |
license.network.url=[url] | Specifies the License Server URL. Include the protocol and host name or IP address and, if appropriate, the port number and context path. Example: |
license.network.user=[username] | Specifies the username for authentication on the secondary DTP server specified with the This options requires the Example: |
license.network.password=[password] | Specifies the password for authentication on the secondary DTP server specified with the This option requires the We strongly recommend encoding your password to ensure successful authentication and a secure connection. You can encode your password by running a command line instance of SOAtest with the See CLI Options for additional information. |
license.network.use.specified.server=true|false | This option enables SOAtest to connect to either DTP and License Server, or two instances of DTP simultaneously. Set to If set to |
license.network.auth.enabled=true|false | Enables or disables authentication on the secondary DTP server specified with the This option requires the |
| Specifies the type of license to retrieve from License Server.
Example:
Default: |
soatest.license.autoconf.timeout=[seconds] | Specifies the maximum number of seconds to wait for the license to be automatically configured from License Server. Default: |
soatest.license.local.password=[password] | Specifies the local password provided to you by Parasoft. |
soatest.license.wait.for.tokens.time=[time in minutes] | Specifies how long to wait for a license if a license is not currently available. Example:
Default: |
OIDC Settings
Setting | Purpose |
---|---|
oidc.enabled=true|false | Enables or disables user authentication via OpenID Connect. Default: |
oidc.issuer.uri=[uri] | Specifies the URI of the OpenID Connect server. Example: |
oidc.client.id=[user] | Specifies the ID provided by your OpenID Connect server. |
oidc.client.secret=[password] | Specifies the application's password to the OpenID Connect server. |
oidc.scopes=[list of scopes] | Defines a space-separated list of scopes, which are used during authentication to authorize access to a user's details. Default: |
oidc.cli.mode=devicecode|certificate | Specifies the method that will be used to authenticate the user on the OpenID Connect server. Default: |
oidc.devicecode.token.file=[path] | Specifies the path to the custom token file containing user authentication information. Example: |
Technical Support Settings
Setting | Purpose |
---|---|
techsupport.auto_creation=true|false | Determines whether archives are automatically prepared when testing problems occur. Default: |
techsupport.send_email=true|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: |
techsupport.archive_location=[directory] | Specifies where archives are stored. |
techsupport.verbose=true|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 in a temporary folder:
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: |
techsupport.verbose.scontrol=true|false | Determines whether verbose logs include output from source control commands. Note that the output could include fragments of your source code. Default: |
techsupport.item.general=true|false | Determines whether general application logs are included. Default: |
techsupport.item.environment=true|false | Determines whether environment variables, JVM system properties, platform details, additional properties (memory, other) are included in the archive. Default: |
techsupport.advanced=true|false | Specifies if advanced options will be sent. Default: |
techsupport.advanced.options=[option] | Specifies any advanced options that the support team asked you to enter. |
Authorship/Scope Settings
Setting | Purpose |
---|---|
authors.mapping{n}=[from_user, to_user] | Specifies a specific author mapping for For example:
|
authors.user{n}=[username, email, full_name] | Specifies a specific author name and email for For example:
|
authors.ignore.case=true|false | 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: |
scope.sourcecontrol=true|false | Determines whether code authorship is computed-based on a data from a supported source control system. Default: |
scope.local=true|false | Determines whether code authorship is computed based on the local user. Default: |
scope.recommended.computation=first|random | Determines how the Recommended Tasks are selected for each team member. You can set the following modes:
|
scope.xmlmap=true|false | 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: |
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
Git Repository Definition Properties
Property | Description |
---|---|
scontrol.rep.type=git | Git 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 (for example, git://hostname/repo.git ). |
scontrol.rep.git.workspace= | The directory containing the local git repository. |
Perforce Repository Definition Properties
Property | Description |
---|---|
scontrol.perforce.exec= | Path to external client executable (p4 ). |
scontrol.rep.type=perforce | Perforce repository type identifier. |
scontrol.rep.perforce.host= | Perforce server host. |
scontrol.rep.perforce.port= | Perforce server port. Default port is 1666. |
scontrol.rep.perforce.login= | Perforce username. |
scontrol.rep.perforce.password= | Password. |
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). |
Subversion Repository Definition Properties
Property | Description |
---|---|
scontrol.rep.type=svn | Subversion repository type identifier. |
scontrol.rep.svn.url= | Subversion URL specifies protocol, server name, port and starting repository path (e.g., svn://buildmachine.foobar.com/home/svn). |
scontrol.rep.svn.login= | Login name. |
scontrol.rep.svn.password = | Password (not encoded). |
scontrol.svn.exec= | Path to external client executable (svn ). |
Microsoft Team Foundation Server Repository Definition Properties
Property | Description |
---|---|
scontrol.rep.type=tfs | TFS repository type identifier. |
scontrol.tfs.sdk.path= | Path to the root directory of the unzipped TFS SDK. This is required for TFS support to work on your machine. Example: Note: TFS SDK version 14.134 is required. |
scontrol.rep.tfs.url= | TFS repository URL (for example, http://localhost:8080/tfs ). |
scontrol.rep.tfs.login= | TFS username. |
scontrol.rep.tfs.password= | TFS password. |
File Encoding Settings
Setting | Purpose |
---|---|
fileencoding.mode=default|user|auto | Defines how file encoding is calculated.
Default: |
fileencoding.user-encoding=<name_of_encoding> | If Valid names are ASCII-US, UTF-8, UTF-16, UTF-16LE, UTF-16BE or java.nio canonical name. It should be specified in form |
fileencoding.auto-language=<language’s numeric_code> | If
|
Miscellaneous Settings
Setting | Purpose |
---|---|
tasks.clear=true|false | Clears existing tasks upon startup in cli mode. This prevents excessive time being spent "loading existing results." Default: |
console.verbosity.level=low|normal|high | Specifies the verbosity level for the Console view. Available settings are:
Default: |
soatest.custom.rules.dir=[directory] | Indicates where user-defined rules are saved. |
soatest.custom.configs.dir=[directory] | 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 (for example, Windows, Linux), an architecture (for example, x86, x86_64), a compiler, a browser, and so on. 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. |
issue.tracking.tags=[value] | Specifies custom issue tracking tags. Multiple tags can be separated by a comma. For example:
For more details, see Associating Tests with Development Artifacts. |
parallel.mode=Manual|Auto|Disabled | Determines which of the following modes is active:
For more details on this and other parallel processing options, see Configuring Parallel Processing. Default: |
parallel.max_threads=<number> | 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] |
parallel.free_memory_limit=<percentage> | 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: |
parallel.no_memory_limit=true|false | Indicates that you do not want to place any restrictions (beyond existing system limitations) on the available memory. Default: |
usage.reporting.enabled=true|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: |
Additional Options for SOAtest and Virtualize
Setting | Purpose |
---|---|
| Specifies the location of JDBC driver jar files and class folders. Special characters (spaces, slashes, colons, and so forth) must be escaped, for instance: %20 = SPACE If listing multiple jars, use \n as a delimiter. For example, becomes
|
scripting.jython.path | Used to add a list of directories to search for python modules that are not already included with Jython. Multiple paths can be listed using the OS default path separator (";" for Windows and ":" for Linux and macOS). |
scripting.timeout.minutes | Specifies the number of minutes after which the product will attempt to stop an unresponsive script and log an error message. |
| Specifies which jar files and class folders are in the classpath. For example:
|
xml.conversion.data.model.directories | Registers 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_path | Specifies 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 Proxy Configuration Details 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." |
browsertesting.http_traffic_timeout=[seconds] | 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|false | During 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.iframes | Enables you to determine whether the contents of hidden frames are displayed in the pre- and post-action HTML viewer. |
security.trust.all.certificates | Indicates that you want to accept any certificate. This is useful if you want to load pages whose certificates are not "trusted." |
security.use.default.java.cacerts | Indicates 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.
Setting | Purpose |
---|---|
server.startup | Determines whether the server is automatically started upon Virtualize startup. |
server.port.http | Specifies the port that the Virtualize Server uses for HTTP. |
server.port.https | Specifies the port that the Virtualize Server uses for HTTPS. |
server.port.monitoring | Specifies the port that the Virtualize Server uses for monitoring. |
traffic.wizard.xpath.ignores | Exclusions are specified in the format:
For example,
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)
Setting | Purpose |
---|---|
env.manager.server | Specifies location of the CTP server. Required Example: |
env.manager.server.name | Specifies the name that will be used to label this server in CTP. You can specify any value that helps you identify this server. Optional Example: |
env.manager.notify | Determines whether the Virtualize server notifies CTP when virtual assets are deployed. Optional Example: |
env.manager.username | Specifies the username for logging into CTP. Optional Example: |
env.manager.password | Specifies the password for logging into CTP. Optional Example: We strongly recommend encoding your password to ensure successful authentication and a secure connection. You can encode your password by running a command line instance of SOAtest or Virtualize with the See CLI Options for additional information. |
Sample Settings
Example 1
# Report settings report.developer_errors=true report.developer_reports=true report.format=html session.tag=<project name> # Mail settings: report.mail.enabled=true report.mail.cc=<[email protected];[email protected]> report.mail.server=mail.company.com report.mail.domain=company.com report.mail.subject=<Static Analysis results on Project X> report.mail.attachments=true
Example 2
# Mail settings report.mail.enabled=true report.mail.server=mail.mycompany.com report.mail.domain=mycompany.com report.mail.cc=project_manager report.mail.subject=Coding Standards
Example 3
# REPORTS #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. report.mail.enabled=true #Exclude developers emails (true/false) report.mail.exclude.developers=false # Append developers errors to manager emails (true/false) report.developer_errors=true # Send reports to developers (true|false) report.developer_reports=true # Append suppressed messages (true|false) report.suppressed_msgs=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} @domain.com # mail target for unknown developer errors [email protected] #Specifies the mail server used to send reports. report.mail.server=mail_server.domain.com #Specifies the mail domain used to send reports. report.mail.domain=domain.com #Specify mali from report.mail.from=nightly #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. report.mail.exclude=developer1;developer2 # Specifies the subject line of the emails sent. report.mail.subject= ${tool_name} Report - ${config_name} # Report test params include (true|false) report.test_params=true # SCOPE #code authorship based on CVS scope.sourcecontrol=true #code authorship based on author tag scope.author=false #code authorship based on local user scope.local=false # LICENSE #override license settings #soatest.license.autoconf.timeout=40 soatest.license.use_network=true soatest.license.network.url=http://license_server.domain.com:2222 soatest.license.network.edition=server_edition # SOURCE CONTROL scontrol.rep1.type=cvs scontrol.rep1.cvs.root=:pserver:developer@cvs_server.domain.com:/home/cvs/scontrol.rep1.cvs.pass=mypassword