...

• 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)—not chrome.
• Safari Executable Path: Specifies the path to the Safari executable.

• Anchor
  proxy-port-field proxy-port-field

  Proxy port: Specifies the proxy port. See Proxy Configuration Details below for more information and tips.
• 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 , 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 

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

...

To manually create a support archive:

• Choose Parasoft> Preferences

...

• , select the Technical Support category

...

• , select the desired archive options

...

• , then click Create Archive.

To open the Technical Support Archive Manager, which allows you to review, e-mail, or delete recent support archives:

• Choose Parasoft> Preferences

...

• , select the Technical Support category

...

• , then click Browse Recent Archives.

Enabling Debug Logging

You can add the following system properties when starting Virtualize from the command line to enable debug logging and to ensure that the all relevant information is included when creating a support archive.

...

Specifies the preconfigured JAR file shipped withVirtualize that contains logging settings. This is the recommended property to use for enabling logging.

...

When creating a support archive it is best to ensure that it contains all the info which is relevant to the  problem and does not contain any unrelated info. To ensure that detailed logs are sent to the standard output console, add the following argument to virtualizecli:

-J-

...

Dcom.parasoft.xtest.logging.config.jar.file=/com/parasoft/xtest/logging/log4j/config/

...

eclipse.

...

on.xml

...

-J-Dparasoft.logging.config.file=<PATH_TO_LOG4J_CONF_FILE>

MIME Type Settings

MIME Type Settings

The MIME Types panel lets you add and remove MIME types. In addition, it lets you specify the location of your preferred text and XML editors and lets you specify what editor you want to use to edit all files that have a particular MIME type.

...

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
JCE Prerequisite JCE Prerequisite

SOAtest and Virtualize ship with their own instance of Java that include the Unlimited Strength Java Cryptography Extension so that they can perform security operations that In order to perform security operations that use XML Signature Verifier, XML Signer, or XML Encryption tools—or to use Key Stores— you will need to download and install the Unlimited Strength Java Cryptography Extension. You can do this as follows:

1. Go to http://www.oracle.com/technetwork/java/javase/downloads/index.html.
2. Download the JCE Unlimited Strength Jurisdiction Policy Files.
3. Install the downloaded files in into the following directory on your machine:
   <Parasoft Test install dir>\<version>\plugins\com.parasoft.xtest.jdk.eclipse.core.<platform>_<jre version>\jdk\jre\lib\security
   For example:
   C:\Program Files\Parasoft\Test\9.10 for SOAtest & Virtualize\plugins\com.parasoft.xtest.jdk.eclipse.core.win32.x86_64_1.8.0.102\jdk\jre\lib\security
   Be sure to replace the existing local_policy.jar and US_export_policy.jar files with the new ones that you downloaded.

4. Restart SOAtest and/or Virtualize.

tools, and Key Stores. If you installed SOAtest or Virtualize from the update site (see Eclipse p2 Update Site Installation) and are using your instance of Java, you will need to download and install the unlimited JCE if it's not already on your system. Refer to the Oracle website for downloads and documentation. MacOS users should install Java 8 newer than update 161 to get the unlimited JCE.

Anchor
Server Settings Server Settings

Server Settings

...

...