...
Table of Content Zone | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
This option sets the property to accept the Parasoft End User License Agreement (EULA). The default is false. You must accept the EULA to use the product. Please read the EULA at https://www.parasoft.com/license. Example Usage
working.dirThis option specifies an absolute path to the SOAVIRT working directory. If not specified, a default working directory called ‘workspace’ is created in the <SOAVIRT_HOME> folder. We recommend changing the default directory so that the workspace is not under the <SOAVIRT_HOME> folder because upgrading to a newer version of the server could overwrite the workspace. logging.config.fileThis option changes the logging level using a built-in or custom log4j2 configuration. If not specified, the default value is /WEB-INF/default.logging.xml. You can specify a configuration using an absolute path or a relative path. The root for relative paths is the <SOAVIRT_HOME> directory location. The server ships with two built-in configurations available in the /WEB-INF/ folder:
You can modify these built-in configurations as needed; see the log4j2 documentation for details. Example Usage
If you unzipped the WAR into c:/wars/soavirt, the server would resolve the relative location of logging.config.file to the absolute path c:/wars/soavirt/WEB-INF/default.logging.xml.
scripting.timeout.minutesThis option specifies the number of minutes after which Virtualize will attempt to stop an unresponsive script and log an error message. The default is 10 minutes. Example Usage
server.hostnameThis options specifies the hostname that CTP will use to connect to the server. Under most circumstances, this option does not require configuration. If the server container or network infrastructure prevents the connection from being established, however, the option may be necessary if the remote host can not determine a valid way to connect back to the server. This may be the case when working with containerized environments. server.port.httpThis option tells CTP which port Parasoft Virtualize Server is listening to for HTTP. You must specify either server.port.http or server.port.https port. This value must match the HTTP port under which Parasoft Virtualize Server is deployed. server.port.httpsThis option tells CTP which port Parasoft Virtualize Server is listening to for HTTPS. You must specify either server.port.https or server.port.http port. This value must match the HTTPS port under which Parasoft Virtualize Server is deployed. env.manager.serverThis option specifies the location of the CTP server. Be sure to specify the port and protocol (http/ https). Colons must be escaped with the backslash \ character. Example Usage
Setting the Property with the REST API
You can also set this property after the server has been started using the REST API. Note that settings related to CTP in the .properties file are named "env.manager", which refers to the legacy name Environment Manager. The CTP object in the API, however, is labeled "ctp". These settings refer to the same component.
You can copy the following example JSON, paste it into your input field, and change the values to your installation:
env.manager.server. nameThis option specifies the name that will be used to label this server on CTP. You can use any value that helps you identify this server. Example Usage
Setting the Property with the REST APIYou can also set this property after the server has been started using the REST API. See env.manager.server for details. env.manager.usernameThis option specifies the username for logging into CTP. Example Usage
Setting the Property with the REST APIYou can also set this property after the server has been started using the REST API. See env.manager.server for details. env.manager.passwordThis option specifies the (plain text or encoded) password for logging into CTP. We strongly recommend running a command line instance of SOAtest or Virtualize with the
The command line tool will generate an encoded string that you can use in place of the password property in the SOAtest and Virtualize Server configuration file. See CLI Options for additional information. Example Usage
Setting the Property with the REST APIYou can also set this property after the server has been started using the REST API. See env.manager.server for details. env.manager.notifyThis option enables/disables notifications to Parasoft CTP when virtual assets are deployed. Example UsageThe following example enables notifications:
Setting the Property with the REST APIYou can also set this property after the server has been started using the REST API. See env.manager.server for details. env.manager.registry.idThis is a read-only setting used by CTP. soatest.license.enabledThis option enables/disables the license related to SOAtest functionality. The default is Example Usage
virtualize.license.enabledThis option enables/disables the license related to Virtualize functionality. The default is Example Usage
soatest.license.use_networkThis option enables/disables licensing over a network. If you are using a network license, you must also configure either a connection to License Server or to Parasoft DTP. Configure the following options to connect to License Server: Configure the following options to connect to DTP: Example UsageThe following example enables licensing over a network:
soatest.license.network.editionThis option specifies the type of license to retrieve from License Server or DTP. You can specify either Example Usage
soatest.license.custom_edition_featuresThis option specifies a comma separated list of features that should be requested for a custom edition license from License Server or DTP. Contact your Parasoft representative if you are unsure of which features you should specify. Example Usage
virtualize.license.use_networkThis option enables/disables licensing over a network. If you are using a network license, you must also configure either a connection to Parasoft DTP or to License Server (deprecated). Configure the following options to connect to License Server: Configure the following options to connect to DTP: Example UsageThe following example enables licensing over a network:
virtualize.license.network.editionThis option specifies the type of license to retrieve from DTP or License Server. You can specify either Example Usage
virtualize.license.custom_edition_featuresThis option specifies a comma separated list of features that should be requested for a custom edition license from DTP or License Server. Contact your Parasoft representative if you are unsure of which features you should specify. Example Usage
dtp.serverurlThis option specifies the host name URL of the DTP server. Include protocol and host name or IP address and, if appropriate, port and context path. Example Usage
dtp.server (deprecated)This option specifies the host name of the DTP server. You must also set the Example Usage
dtp.port (deprecated)This option specifies the port number of the DTP server. You must also set the Example Usage
dtp.userThis option specifies the user name for DTP authentication.You must also set the Example Usage
dtp.passwordThis option specifies the password for DTP authentication.You must also set the Example Usage
license.network.urlThis option specifies the URL of the License Server. Include protocol and host name or IP address and, if appropriate, port and context path. Example Usage
license.network.hosthost (deprecated)This option specifies the host name of the License Server. You must also set the license.network.port (deprecated)This option specifies the host port of the License Server. You must also set the license.network.userSpecifies the username for authentication on the secondary DTP server specified with the Example: license.network.passwordSpecifies the password for authentication on the secondary DTP server specified with 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 or Virtualize with the
The command line tool will generate an encoded string that you can use in place of the password property in the SOAtest and Virtualize Server configuration file. See CLI Options for additional information. license.network.use.specified.serverThis option enables the server to connect to connect to either DTP and License Server or two instances of DTP simultaneously. If set to license.network.connection.typeThis option specifies whether to connect to DTP/License Server over HTTP or over TCP. HTTP over a secure port (SSL) is recommended. Default is license.network.auth.enabledEnables or disables authentication on the secondary DTP server specified with the This option requires the virtualize.license.local.passwordThis option specifies the password for the local Virtualize license. You must also set the virtualize.license.local.expirationThis option specifies an expiration for the local Virtualize license. You must also set the usage.reporting.enabledThis setting 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. Example UsageThe following example enables anonymous usage data reporting:
|
...
Table of Content Zone | ||||||
---|---|---|---|---|---|---|
| ||||||
session.tagThis setting specifies a tag for signing results from the test session. The tag can be a string, one or more variables, or a combination. Reports for different test sessions should be marked with different session tags so that similar runs can be distinguished from each other. The default is Example UsageYou can use the session tag to represent a specific analysis type made on a specific code branch in a specific test environment. The following configuration could identify functional tests on the master branch for different operating systems:
build.idThis setting specifies a build identifier used to label results. It may be unique for each build, but it may also label more than one test session executed during a specified build. The default is Example UsageThe default build ID includes the name of the project in DTP and the date of the build. For example, for the ATM project, the build ID included in the report may resemble the following: ATM-2017-07-07. The following configuration specifies the custom build ID that consists of the name of the project and the build number passed via the environmental variable
For the ABC project and the build number 114 on a CI server, this may resolve to report.formatThis setting specifies the report format. Use a comma separated list of format values to publish reports in more than one format. By default, an XML report containing the data and an HTML file for presenting the data are published. The following values are supported:
report.custom.extensionThis setting specifies the file extension for a custom report. Custom formats are defined in an XSL file. The report.format option must be set to custom and the report.custom.xsl.file option must also be configured. report.custom.xsl.fileThis setting specifies the path to an XSL file used to create a custom report format. Use double backslashes when specifying the file path on Windows. report.developer_errorsThis setting determines if details about developer errors should be included in manager reports. Set to report.developer_reportsThis setting determines if detailed reports for all developers should be generated in addition to the summary report for managers. Set to report.authors_detailsThis setting determines if an overview of the number and type of tasks assigned to each developer should be included in the report. Set to report.testcases_detailsThis setting determines if additional test case details should be included in the report. Set to report.associationsThis setting enables or disables showing requirements, defects, tasks, and feature requests associated with a test in the report. Set to report.assoc.url.[tag]This setting generates a link to an association inside the HTML report. The URL is a query string containing an [%ID%] or Example UsageThe following example creates a link to a PR in Bugzilla in the HTML report:
report.failed_tests_onlyThis setting determines if only tests that failed should be included in the report. This option is only valid for functional testing tools. Set to report.env_detailsThis setting turns on additional details in the XML report about the active environment used when running a tst. The default is false. report.output_detailsThis setting turns on additional details in the XML report about output tools that were executed when running a tst. The default is false. report.test_suites_onlyThis setting determines if summary section of the report lists only top-level suites or if it displays a tree-like view of the individual tests. Set to |
...