...
- Show tool descriptions: Enables/disables showing tool descriptions in applicable wizards.
- Auto Beautify: Tells SOAtest to automatically beautify XML messages in the selected tool or tools (Traffic Viewer, Diff, Editor) if the message is under the specified size (10 KB is the default setting).
- Masked Environment Variables: Enable to hide any masked environment variables from traffic viewers, REST Clients, JSON/XML Data Banks and Assertors, and in the Event Monitoring Details. See Masking a Variable Value for more information about masking environment variables.
- Character Encoding: You can enable System default to configure SOAtest and/or Virtualize to use the default character set for the particular system being used. Enable Custom to encode characters from the list of encodings available on the JVM being used.Save settings: Specifies what file format to use for saving project files (for example, .pva, .pvn, .changetemplate). (for example, .tst, .changetemplate). See Understanding the Available Project File Formats.
- Default timeout (milliseconds): Allows you to enter the length of delay (in milliseconds) after which SOAtest should consider your FTP, telnet, or HTTP requests to be “timed out.” The default is 30000 milliseconds.
- Report each duplicate error that occurs on the same line: Tells SOAtest to show only the first instance of duplicate errors that occur for the same line of code.
- Reset Cookies: Allows you to clear the current global cookies so that next HTTP invocations start a new session: Allows you to clear the current global cookies so that next HTTP invocations start a new session.
- Save settings: Specifies what file format to use for saving project files (for example, .tst, .changetemplate). See Understanding the Available Project File Formats.
- Enable the Automatically backup project files option and specify a file size threshold for .tst and/or .pva files in the Warn on file size large than (MB) field to be notified when the size of the file exceeds the threshold. You can then reduce the size (and prevent performance problems) by dividing it into smaller files.
...
The OpenAI panel allows you to configure the application to use your OpenAI or Azure OpenAI account to assist you when creating test scenarios. The model of OpenAI that is used must support function calling. Functionality has been tested on GPT-3.5 turbo and GPT-4 and the embedding model text-embedding-ada-002. Note this functionality is only supported with a license that has "LLM Integration" enabled.
...
Enable: When enabled, OpenAI is available when creating test scenarios from an OpenAPI/Swagger definition.
- Provider: Your OpenAI provider. Choose between OpenAI and Azure OpenAI.
- Configuration (OpenAI)
- API key: Your OpenAI token.
- Organization ID: The Organization ID you want to use when accessing the OpenAI client. Optional. If no Organization ID is supplied, the default organization ID for your account will be used.
- Test Connection: Click to test the connection to OpenAI.
- Model > NameGPT: The name of the OpenAI GPT model you are using, for example gpt-3.5-turbo-16k or gpt-4.
- Embedding: The name of the Embedding model you are using, for example text-embedding-ada-002.
- Configuration (Azure OpenAI)
- Resource Name: The Azure resource that contains your deployed Azure OpenAI model.
- API key: Your Azure OpenAI token.
- GPTDeployment ID: The deployment name of your Azure OpenAI GPT model.
- API key: Your Embedding: The deployment name of your Azure OpenAI tokenEmbedding model.
- Test Connection: Click to test the connection to Azure OpenAI.
...
| Note | ||
|---|---|---|
| ||
Eclipse users: If you are going through a proxy to connect to your OpenAI or Azure OpenAI account, your Eclipse proxy settings are used, not your Parasoft proxy settings. |
| Anchor | ||||
|---|---|---|---|---|
|
| Info |
|---|
CTP and DTP or PSTSec are required for OpenID Connect in SOAtest and Virtualize. |
The OpenID Connect panel allows you to configure the application application to authenticate users via your OpenID Connect server by setting the following:
...
You can specify the trust store, key store, and key store password for clients that interact with AUTs over MQ SSL. These settings are not applicable to Virtualize. If you need to configure virtual assets that transport MQ messages over SSL, see Configuring Server and Deployment Settings Virtualize. For details on MQ SSL settings, see IBM WebSphere MQ > SSL.
JCE Prerequisite
| Anchor | ||||
|---|---|---|---|---|
|
...
- Default Transport: Allows you to set the default transport protocol.
Attachment Encapsulation Format: Allows you to choose MIMENone, DIMEMTOM always, or MTOM , optional for the default attachment encapsulation. See See Working with Attachments for details.
- SOAP Version: Allows you to select SOAP 1.1 or SOAP 1.2.
- Outgoing Message Encoding: Allows you to choose the encoding for outgoing messages. You can choose any Character Encoding you wish to read and write files, but the Outgoing Message Encoding provides additional flexibility so you can set a different charset encoding for the SOAP request.
...
| Setting | Purpose | ||
|---|---|---|---|
virtualize.license.use_network=true|false | Determines whether the current installation retrieves its license from License Server. | ||
virtualize.license.network.host=[host] | Specifies the machine name or IP address of the machine running License Server Configuration Manager. If your server uses the HTTPS protocol, prepend This setting is deprecated. | ||
virtualize.license.network.port=[port] | Specifies the License Server port number. This setting is deprecated. | ||
virtualize.license.network.user=[username] | Specifies the username for authentication on the secondary DTP server License Server specified with the This option requires the Example: | ||
virtualize.license.network.password=[password] | Specifies the password for authentication on the secondary DTP server License 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 Example:
The command line tool will generate an encoded string that you can use in the configuration file. you can use in the configuration file. | ||
license.network.url=[url] | Specifies the License Server URL. Remember to include the | 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.context.path=[path] | Specifies the path to the DTP License Server. The context path is a relative path from the host name specified with the Configuring the context path is not supported for standalone License Server. Refer to the DTP documentation for additional information about reverse proxy server configuration and context path configuration. This setting is deprecated. | ||
license.network.auth.enabled=true|false | Enables or disables authentication on the secondary DTP server License Server specified with the This option requires the | ||
license.network.use.specified.server=[true|false] | This option enables Virtualize to connect to either DTP and License Server, or two instances of DTP simultaneously. Set to If set to | ||
virtualize.license.network.edition=[edition_name] | Specifies the type of license that you want this installation to retrieve from LicenseServerthe License Server.
Example:
| ||
virtualize.license.autoconf.timeout=[seconds] | Specifies the maximum number of seconds this installation will wait for the license to be automatically configured from LicenseServerthe License Server. Default is is 10. | ||
virtualize.license.local.expiration=[expiration] | Specifies the local license that you want this installation to use. | ||
virtualize.license.local.password=[password] | Specifies the local password that you want this installation to use. | ||
virtualize.license.wait.for.tokens.time=[time in minutes] | Specifies the time that this installation will wait for a license if a license is not currently available. For example, use |
...
| Setting | Purpose | ||
|---|---|---|---|
dtp.autoconfig=true|false | Enables autoconfiguration with Parasoft Test settings stored on the DTP server. Default: | ||
dtp.enabled=true|false | Determines whether the current Parasoft Test product is connected to DTP. Default: product is connected to DTP. Default: | ||
dtp.url=[url] | Specifies the DTP URL. Remember to include the https:// protocol; DTP does not support http:// connections. If DTP is deployed to a location other than the root of the host server, the URL should include a context path (a relative path from the host name; for example: https://server.company.com:8443/contextPath). This may be the case if your organization uses a reverse proxy. Refer to the DTP documentation on https://docs.parasoft.com for additional information about reverse proxy server configuration and context path configuration | dtp.url=[url] | Specifies the URL of the DTP server. Include protocol and host name or IP address and, as appropriate, port and context path. |
dtp.server=[host] | Specifies the host name of the DTP server. This setting is deprecated. | ||
dtp.port=[port] | Specifies the DTP server port. This setting is deprecated. | ||
console.verbosity.level=low|normal|high | Specifies the verbosity level for the Console view. Available settings are:
| ||
parallel.mode=Manual|Auto|Disabled | Determines which of the following modes is active:
| ||
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. | ||
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. | ||
parallel.no_memory_limit=true|false | Indicates that you do not want to place any restrictions (beyond existing system limitations) on the memory available to the product. | ||
tasks.clear=true|false | Clears existing tasks upon startup in cli mode. This prevents excessive time being spent "loading existing results." The default is true. | ||
security.trust.all.certificates=true|false | Tells Virtualize that you want it to accept any certificate. This is useful if you want to load pages whose certificates are not "trusted." | ||
security.use.default.java.cacerts=true|false | Tells Virtualize that you want it to accept only certificates from the standard list of Java trusted certificate vendors. |
...
- If you will be using a custom edition license, define the appropriate license features in the settings as follows:
[product].license.custom_edition_features= All enabled features
Note that license feature settings apply only to custom edition licenses. Define the main license settings in the settings as follows:
Code Block virtualize.license.network.edition=[Type of license edition] virtualize.license.use_network=[Value (true or false)] license.network.url=[URL]
If your server uses the HTTPS protocol, Remember to prepend
https://to the hostname.http://connections are not supported.
Here are several examples of properly configured license settings in settings file:
...
| Code Block |
|---|
virtualize.license.network.edition=desktop_edition virtualize.license.use_network=true license.network.url=httphttps://main1server.parasoftdomain.com.pl:22228443 |
Virtualize network license -custom edition with various features
| Code Block |
|---|
virtualize.license.custom_edition_features=Virtualize, Server, Message Packs, Unlimited Million Hits / Day virtualize.license.network.edition=custom_edition virtualize.license.use_network=true license.network.url=httphttps://main1server.parasoftdomain.com.pl:22228443 |
Virtualize network license -custom edition with various features
...
Note that with local licenses, the enabled features are specified via the generated password.
...