...
Firefox Executable Path: Specifies the path to the Firefox executable. On Windows machines, SOAtest and/or Virtualize will attempt to detect a Firefox installation automatically. Linux users will have to browse to the Firefox executable.
- Chrome Executable Path: Specifies the path to the Chrome executable. Paths set here will be used in web recording wizards and other applicable areas. On Linux, choose
google-chrome(e.g. /opt/google/chrome/google-chrome)—notchrome.
Proxy port: Specifies the proxy port. See Additional Preference Settings Proxy Configuration Details below for more information and tips.Anchor proxy-port-field proxy-port-field - Browser communication port: Specifies the browser communication port.
Browser Timeout Settings: Specifies the length of delay (in milliseconds) after which SOAtest and/or Virtualize should stop waiting for browser startup or a user action and consider it to be "timed out."
Wait Condition Default Timeout Settings: Specifies the length of delay (in seconds) after which SOAtest and/or Virtualize should stop waiting for the activity specified in the wait condition to occur and consider it to be "timed out."
Debug Options> Print debugging information: During recording of a web scenario, it is possible that an action taken is not recorded by SOAtest and/or Virtualize. Enabling this option will allow messages to be printed to the message console during recording, with information about what events SOAtest and/or Virtualize handled, any locators that may have been generated, and if applicable, any exceptions that took place during recording.
Error Reporting> Report website's scripting errors: Configures SOAtest and/or Virtualize to report scripting errors that occur during scenario execution. In Internet Explorer, the Selenium Web-Driver framework will not report JavaScript errors on the page to SOAtest and/or Virtualize; this reporting is supported only for the legacy engine.
- Allowable Binary Files in Traffic Viewer and Outputs: Allows binary files with the specified extensions or MIME types to be used in the Traffic Viewer and output. By default, only text files will be allowed.
Browser Contents Viewer Rendering Engine: Enables you to specify what browser is used for the Browsear Contents Viewer tool(described in Browser Contents Viewer) , which can be attached to the Browser Playback tool.
- The default option (Same browser used for playback) is generally the recommended option because some web applications generate their pages differently based on the browser used. Using the same browser that was used during the playback can help ensure that pages display properly in the Browser Contents Viewer. Note that if the playback browser was Chrome, the Firefox rendering engine is used.
When Internet Explorer is selected, the version of IE that is used depends on what version of IE is installed on the machine running SOAtest and/or Virtualize. The Internet Explorer option is available only on Windows.
When Firefox is selected, the version of Firefox that is used depends on what Eclipse is being used to run SOAtest and/or Virtualize. It can range from Firefox 3.0.1 to Firefox 10, depending on what OS is being used.
- If the particular web application being tested does not render properly in the Browser Contents Viewer, you could try configuring this option to use either Internet Explorer or Firefox specifically (rather than use the default Same browser used for playback option) to see if using a specific rendering engine will improve how the page is shown in the Browser Contents Viewer.
HTML Content Fetch Mode: Enables you to determine whether the contents of hidden frames are displayed in the pre- and post-action HTML viewer. This can impact record and playback speed, as well as file size. It is possible to use one mode on some of your team’s SOAtest and/or Virtualize machines (e.g., desktop installation), and a different mode on others (e.g, the Server machine running in command-line mode).
Fetch all HTML content Choose this option if you want to see the contents of hidden frames in the pre- and post-action HTML viewer (in the Browser Playback tool, Browser Contents Viewer, Browser Data Bank, and Browser Validation tool). This is desirable if you want to create validations/extractions in hidden iframes. This mode will significantly slow down recording and playback. Moreover, it will significantly increase .tst file size if your application uses hidden iframes.
Fetch content for all content except hidden frames: Choose this option if you do not need to see the contents of hidden frames in the pre- and post-action HTML viewer.(in the Browser Playback tool, Browser Contents Viewer, Browser Data Bank, and Browser Validation tool). In this mode, the browser will still retrieve all frames from the server and it can still perform validations and extractions on the hidden iframes. However, it will not display the contents of hidden frames in the pre- and post-action HTML viewer.
...
The default host and port for the internal proxy is localhost:55555. Change the port number if this port is already in use using the controls Proxy port field. Do not change this from within the browser.
If your machine is configured to use your own proxy, you should configure SOAtest and/or Virtualize to point to that proxy. This enables SOAtest and/or Virtualize to configure its internal proxy to forward all traffic to the specified proxy configured in Additional Preference Settings Proxy Settings.
Internet Explorer Notes
SOAtest and Virtualize modify the global registry settings prior to starting its instance of the browser. If an instance of Internet Explorer was running on the machine prior to launching SOAtest or Virtualize (not recommended), the global registry settings will not be set in the existing browser instance.
...
Global data sources can be reused and shared outside of a single SOAtest project and across Virtualize deployments. The Global Data Source panel lets you determine how information about global data sources is saved. For information on how to configure global data sources, see Adding a Data Source at the Test Responder Suite, Project, or Global Level and Adding a Data Source at the Test Suite, Project, or Global Level.
Technical Support Settings
...
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, seeAdditional Preference Settings Proxy Configuration Details).
- 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, then enter the proxy address in the Address field.
- If you want to use the same proxy server for all protocols, check the Same proxy server for all protocols check box, 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, clear the Same proxy server for all protocols check box, 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, check the Enable proxy authentication check box, then enter a valid user name 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 befile:///home/machine/scripts/proxy.pac.
...
- Enables the Perform Authentication option and enter the Username and Password to authenticate the request
- Choose the authentication type from the drop-down menu. Supported types are Basic, NTLM, Kerberos, or Digest.
- If you are using Kerberos authentication, enter the Service Principal to authenticate the request. If the correct username and password, or the correct service principal, are not used, the request will not be authenticated.
- Kerberos realm: Specify the Kerberos realm associated with your network. By convention, this is typically your domain name in all caps (e.g. PARASOFT.COM).
- KDC server: Specify the hostname of your Key Distribution Center (e.g. kdc.parasoft.com).
- Check Ticket: This will execute a simple test to locate a cached Kerberos TGT (Ticket Granting Ticket) to grant access to the service. SOAtest and/or Virtualize will not be able to communicate with the service if it cannot first locate a valid TGT. For more information about Kerberos, see Additional Preference Settings Configuring Kerberos Authentication.
About Kerberos Authentication
...
| Info | ||
|---|---|---|
| ||
In order to perform operations that use the XML Signature Verifier, XML Signer, or XML Encryption tools, or if using Key Stores, you will need to download and install the Unlimited Strength Java Cryptography Extension. For details, see Additional Preference Settings JCE Prerequisite. |
Keystores are specified at the test or responder suite level. If this option is selected, the following options are available in the Certificate and Private Key tabs:
...
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 | ||||
|---|---|---|---|---|
|
...
| Setting | Purpose |
|---|---|
virtualize.license.use_network=true|false | Determines whether the current installation retrieves its license from LicenseServer. |
virtualize.license.network.host=[host] | Specifies the machine name or IP address of the machine running LicenseServer Configuration Manager. If your server uses the HTTPS protocol, prepend ExampleExamples:
|
virtualize.license.network.port=[port] | Specifies the LicenseServer port number. Example:
|
virtualize.license.network.user=[username] | Specifies the username for authentication on the secondary DTP server specified with the This options requires the Example: |
virtualize.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 Example:
The command line tool will generate an encoded string that you can use in the configuration file. |
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. |
license.network.auth.enabled=true|false | Enables or disables authentication on the secondary DTP 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 Set to |
virtualize.license.network.edition=[edition_name] | Specifies the type of license that you want this installation to retrieve from LicenseServer.
Example:
|
virtualize.license.autoconf.timeout=[seconds] | Specifies the maximum number of seconds this installation will wait for the license to be automatically configured from LicenseServer. Default 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 |
See Additional Preference Settings Manually Adding the License to localsetttings for additional notes and examples.
...
| 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: |
dtp.server=[host] | Specifies the host name of the DTP server. |
dtp.port=[port] | Specifies the DTP server port. |
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.certificatestruecertificates=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.cacertstruecacerts=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 localsettings 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 localsettings as follows:
Code Block virtualize.license.network.edition= Type of license edition virtualize.license.use_network= Value (true or false) license.network.host= Host name license.network.port= Port number
If your server uses the HTTPS protocol, prepend
https://to the hostname.
Here are several examples of properly-configured license settings in localsettings file:
...