Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


LinuxMacOS
Processor32-bit or 64-bit (x86_64) processors with at least 4 cores are supported32-bit or 64-bit (x86_64) processors with at least 4 cores are supported
Software

Java 8 (Oracle and OpenJDK are supported)

GTK+ 2.18 or higher

GLib 2.17.6 or higher

Pango 1.20 or higher

X.Org 1.0 or higher

Java 8 (Oracle and OpenJDK are supported)
Memory

At least 1 GB RAM. 2 GB RAM is recommended.Load Test might require more for high loads.

1 GB RAM minimum. 2 GB RAM is recommended.Load Test might require more for high loads.

OS Versionn/aMac OS X 10.5 9 or higher
Default font size

8 is recommended. For example, on Ubuntu, use the following in the terminal:

gsettings set org.gnome.desktop.interface font-name 'Ubuntu 8'


...

A directory under parasoft/soatest_virtualize/<version> (Linux) or soatest_virtualize/<version>/Parasoft SOAtest & Virtualize/Virtualize.app/Contents/ParasoftSOAtestVirtualize (Mac) will be created. We refer to this location as <soavirt> throughout this user guide. The SOAtest and Virtualize executables, command line interfaces, examples, etc. are available within this directory.


Info
titleAccessing Application Contents on MacOS

After installation is completed, an application icon will be added in Finder. This is the icon that you double-click to launchSOAtest and Virtualize. If you want to view the various files and folders available within the installation, right-click the icon, and choose Show Package Contents

Plug-in Installation

  1. Launch Eclipse and choose Help> Install New Software from the Eclipse menu.
  2. Click Add. 
  3. Click Archive and browse for theparasoft_soavirt_<version>_macosx_x86_64_updatesite_p2.zip archive.

  4. Click Add and select all Parasoft items to install.
  5. Click Finish and restart Eclipse when prompted. 

...

Info
titleFrozen Workspace Launcher?

On Eclipse 4.5 and Mac OS X 10.11, there is a known issue with the workspace launcher freezing (becoming unresponsive) when Virtualize starts up. The workaround is to launch Virtualize from the command line with the –nosplash argument.

See Licensing for details on configuring your license.