In this section:

System Requirements


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.

1 GB RAM minimum. 2 GB RAM is recommended.

OS Versionn/aMac OS X 10.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'


The Parasoft/Eclipse application and system libraries must be for the same architecture. If you are using a 64-bit Linux but you are running the 32-bit (x86) version of Parasoft, you need the 32-bit version of the above libraries. 

Installation

You can install Virtualize as a standalone Eclipse application or as an Eclipse plug-in. 

The standalone version ships with Eclipse 4.6.1, which contains a known defect that may result in IDE crashes on macOS. Eclipse 4.6.1, furthermore, does not run on macOS X if a version of Java newer than 8 is installed. Eclipse 4.8 or later is required to launchVirtualize if a newer version of Java  is installed. Future versions will ship with a newer version of Eclipse to address these issues. 

If you experience issues with the standalone version, we recommend installing Virtualize as a plug-in for Eclipse 4.7 or later.

Standalone Installation


  1. If you haven’t already done so, copy the installation file to the directory where you would like to install Virtualize.
  2. Change directories to the directory where you are going to install Virtualize.
  3. Set "execute" permissions on the installer.
    • chmod +x parasoft_virtualize_<version>_linux.sh
    • chmod +x parasoft_virtualize_<version>_macosx.sh
  4. Execute the installer, then follow the onscreen instructions to complete the installation.
    • ./parasoft_virtualize_<version>_linux.sh
    • ./parasoft_virtualize__<version>_macosx.sh

A directory under parasoft/virtualize/<version> (Linux) or virtualize/<version>/ParasoftVirtualize.app/Contents/ParasoftVirtualize (Mac) will be created. We refer to this location as <virtualize_install_dir> throughout this user guide. The Virtualize executable, command line interface, examples, manuals, etc. are available within this directory.


Accessing 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 launchVirtualize. 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 the parasoft_virtualize_<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. 

Updates

See Service Pack Updates.

Start Up on Linux


To run Virtualize GUI:

  1. Change directories to the virtualize/<version> directory 
  2. Enter the following command at the prompt:
    ./Virtualize

To run Virtualize Command Line:

  1. Change directories to the virtualize/<version> directory 
  2. Enter the following command at the prompt:
    ./virtualizecli



Start Up on MacOS


Double-click the Parasoft Virtualize icon in Finder to start the Virtualize desktop application.

To start Virtualize command line:

  1. Change directories to the virtualize/<version>/ParasoftVirtualize.app/Contents/ParasoftVirtualize directory
  2. Enter the following command at the prompt:
    ./virtualizecli

You must install a license before you begin using Virtualize.

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


  • No labels