In this section:
System Requirements
Linux | MacOS | |
---|---|---|
Processor | 32-bit or 64-bit (x86_64) processors with at least 4 cores are supported | 32-bit or 64-bit (x86_64) processors with at least 4 cores are supported |
Software | Java 8 GTK+ 2.18 or higher GLib 2.17.6 or higher Pango 1.20 or higher X.Org 1.0 or higher | Java 8 |
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 Version | n/a | Mac OS X 10.9 or higher |
Default font size | 8 is recommended. For example, on Ubuntu, use the following in the terminal:
|
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.
SOAtest and Virtualize Co-Installation
When Parasoft SOAtest and Parasoft Virtualize are installed on the same machine, SOAtest and Virtualize must have an identical version number. This ensures compatibility between both products.
If you are updating an existing installation (including updating from a service pack), be sure to update both products at the same time.
Installation
- If you haven’t already done so, copy the installation file to the directory where you would like to install the application.
- Change directories to the destination directory.
- Set "execute" permissions on the installer.
chmod +x parasoft_soavirt_<version>_linux.sh
chmod +x parasoft_soavirt_<version>_macosx.sh
- Execute the installer, then follow the onscreen instructions to complete the installation.
./parasoft_soavirt_<version>_linux.sh
./parasoft_soavirt__<version>_macosx.sh
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.
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 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.
Updates
See Service Pack Updates.
Start Up on Linux
To run SOAtest GUI:
Change directories to the
soatest/9.x directory
, then enter the following command at the prompt:./SOAtest
To run SOAtest Command Line:
Change directories to the
soatest/9.x
directory, then enter the following command at the prompt:./soatestecli
For details on using soatestcli
, see Testing from the Command Line Interface - soatestcli.
To start Load Test:
Change directories to the
soatest/9.x
directory, then enter the following command at the prompt:./loadtest
To run Virtualize GUI:
- Change directories to the
virtualize/<version>
directory - Enter the following command at the prompt:
./Virtualize
To run Virtualize Command Line:
- Change directories to the
virtualize/<version>
directory - Enter the following command at the prompt:
./virtualizecli
Start Up on MacOS
Double-click the Parasoft SOAtest & Virtualize icon in Finder to start the SOAtest and Virtualize desktop application.
You must run command line distributions separately.
To start Virtualize command line:
- Change directories to the soatest_virtualize/<version>/Parasoft SOAtest & Virtualize.app/Contents/ParasoftSOAtestVirtualize directory
- Enter the following command at the prompt:
./virtualizecli
To start SOAtest command line:
- Change directories to the soatest_virtualize/<version>/Parasoft SOAtest & Virtualize.app/Contents/ParasoftSOAtestVirtualize directory
- Enter the following command at the prompt:
./soatestcli
See Load Test Command Line Interface - cli for information on running Load Test from the command line.
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.