...

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

Anchor
OpenAI OpenAI

OpenAI

The OpenAI panel allows you to configure the application to use your OpenAI account to assist you when creating test scenarios. Using OpenAI to create test scenarios requires access to your OpenAI account by setting the following:

• Enable: When enabled, OpenAI is available when creating test scenarios from an OpenAPI/Swagger definition.
• Configuration
  • 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 your OpenAI client.
• Model
  • Name: The name of the OpenAI model you are using. Note that a model that supports functional calls is required. Functionality has been tested on the following models:
    • OpenAI: gpt-3.5-turbo-16k and gpt-4
    • Azure OpenAI: gpt-3.5-turbo-16k

Anchor
OIDC OIDC

OpenID Connect

The OpenID Connect panels panel allows you to configure the application to authenticate users via your OpenID Connect server .

...

by setting the following:

• Enable: When enabled, OpenID Connect is available for authentication.
• Server
  • Issuer URI: The URI of your OpenID Connect server.
  • Client ID: The ID registered on your OpenID Connect server.
  • Client Secret: The application's password to the OpenID Connect server.
  • Scopes: A space-separated list of scopes used during authentication to authorize access to a user's details.
  • Callback host: The local callback host required to communicate with the OpenID Connect server. The following options are available:
    • localhost: The localhost address will be used for communication.
    • 127.0.0.1: The loopback IP address 127.0.0.1 will be used for communication.
  • Callback port: The callback port number for communication with the OpenID Connect server. The following options are available:
    • Automatically select an open port: Automatically selects an open port (recommended).
    • Use port: Allows you to manually specify the port number.
  • Callback timeout: Specifies, in seconds, the maximum time the browser will wait for user credentials.

...

• • Test Authentication

...

• • : Click to open the OpenID Connect authentication page in your browser.

...

• • You may be asked to provide your credentials in the browser window that opens

...

• • .

...

• Status

...

• : Shows the current OpenID Connect authentication status.

...

The Proxy panel controls how SOAtest and/or Virtualize works with proxy servers. It does not control the separate intermediary proxy used for web scenarios (for details on this other proxy, seeProxy Configuration DetailsAdditional Preference Settings). 

• If Windows and IE (which use the same settings) are configured to properly use the proxy to access the relevant websites, select Use system proxy configuration.

• Otherwise, select Enable proxy and manually enter the correct settings. These settings should be equivalent to what you would use in the browser outside of SOAtest/Virtualize.

  • To use an automatic configuration script, select Use automatic configuration script and enter the proxy address in the Address field.
  • If you want to use the same proxy server for all protocols, enable Same proxy server for all protocols, then enter the address and port of the proxy server you want to use in the Proxy Address and Proxy Port fields.
  • If you want to use different proxy servers for different protocols, disable Same proxy server for all protocols, then enter the address and port of each proxy server you want to use in the Proxy Address and Proxy Port fields.
  • If your proxy server requires authentication, enable Enable proxy authentication, then enter a valid username and password in the Username and Password fields.
  • If you want to allow Web traffic from designated IP addresses to pass through directly (avoiding the proxy), enter those IP addresses in the Proxy Exceptions text field. If you enter multiple addresses, use a semicolon (;) to separate the entries.
  • The Proxy Address value should be a URL to the script: either an HTTP(S) URL or a file URL. File URLs should be formatted as "file:///" followed by the file system path where the proxy autoconfiguration script lives. For example, on Windows this could be file:///c:/Users/user/scripts/proxy.pac. On Linux, it might be file:///home/machine/scripts/proxy.pac.

...

The Scripting panel allows you to specify properties used for custom scripts.

• Java: For Java, you can specify the Java home directory and the path to the javac compiler. You need to specify these parameters if you want to compile Java methods in the editor.   

  Note
  title Note
  The javac compiler is not included.

  • Java home: Specifies the Java installation directory.
  • Javac classpath: Specifies the Java classpath.
• JavaScript: If you create scripts using JavaScript, you can specify a script template in the Script Template field.
  • Script Template: Whatever code is specified in this field will be used as the default code for inlined scripting in the language with which the field is associated. This is primarily useful for setting default inputs and common global variables. Script templates apply to scripts used in Extension tools; they do not apply to JavaScript that runs in a browser context.

• Jython: If you are using Jython scripts, you can specify the Jython Path variable. Jython scripting support can be used without setting this variable by specifying a script template in the Script Template field.

  • Jython Path: Specifies a list of directories to search for python modules that are not already included with Jython. Separate multiple directory paths using the OS default path separator (";" for Windows and ":" for Linux and macOS). If you set the Jython path then you need to restart SOAtest or Virtualize for the change to take effect.
  • Script Template: Code specified in this field sets a default template for Jython scripts used in the tool.

• Timeout Settings: Specify how many minutes SOAtest or Virtualize should wait before attempting to stop an unresponsive script and log an error message.

Security Settings

You can configure default security settings for clients and Responders used in your projects. In most cases, the security settings can be overridden by configurations set locally in your suites:

...

The XML Schema Locations panel lets you view, add, and remove schema locations.The XML Validator tool needs to know where to find the schema that it should use to validate the document of concern. In most cases this is a URI and is supplied within the document being validated. If, however, the URI for the schema is not supplied or if you want to use a different location, then disable Use namespace as location URI for Schemas for the XML Validator tool. For more information on the XML Validator tool, see .XML Validator vSOAVIRT_9.10.2_CTP_3.0.2. When the tool is run with this option disabled, SOAtest will use the schema location(s) indicated in this panel. To add a new schema location:

...