|Table of Contents|
- At least 1 GB RAM (2 GB is recommended); Load Test might require more for high loads
- Java 8 or higher
- GTK+ 2.18 or higher
- GLib 2.17.6 or higher
- Pango 1.20 or higher
- X.Org 1.0 or higher
- 32-bit or 64-bit (x86_64) processors with at least 4 cores are supported
- Default font size of 8 is recommended. For example, on Ubuntu, use the following in the terminal:
gsettings set org.gnome.desktop.interface font-name 'Ubuntu 8'
The SOAtest/Eclipse application and the system libraries must be for the same architecture. Thus, if you are using a 64-bit Linux but you are running the 32-bit (x86) version of SOAtest, you need the 32-bit version of the above libraries.
- Mac OS X 10.5 9 or higher
- Java 8 or higher
- Intel® Xeon® 2.0 GHz or higher with at least 2 cores recommended
- 1 GB RAM minimum; 2 GB RAM recommended
A directory under
parasoft/soatest/9.x (Linux) or
soatest/9.x/ParasoftSOAtest.app/Contents/ParasoftSOAtest (Mac) will be created. We refer to this location as
<soatest_install_dir> throughout this user guide. The SOAtest executable, command line interface, examples, manuals, etc. are available within this directory.
After installation is completed, an application icon will be added in Finder. This is the icon that you double-click to launch SOAtest. If you want to view the various files and folders available within
The default SOAtest workspace will be set to
<user_home_dir>/parasoft/workspace. This default workspace is preselected in the Select a Workspace dialog when you first start SOAtest. If you select a different workspace, that new workspace will be preselected when you start SOAtest from that point forward. The command line interface uses the default workspace any time that you do explicitly specify a workspace from the command line (with the
-data argument)—whether or not you have previously run the command line interface with another workspace.
- Double-click the Parasoft SOAtest icon in Finder.
On Eclipse 4.5 and Mac OS X 10.11, there is a known issue with the workspace launcher becoming unresponsive when SOAtest starts up. The workaround is to launch SOAtest from the command line with the
To run SOAtest Command Line: