3.1. Installing from Binary Packages

3.1.1. Getting the Correct Package
3.1.2. Configuring the Package
3.1.3. Using the Binary Package

Squish can be installed from binary packages, which simply need to be unpacked and then configured before they are ready for use. Binary packages are available for Linux®, OS X® and MicrosoftWindows®. Since Squish integrates very tightly with your computer's system and with the application/website you want to test, different versions of each package are available. Hence, the first step when installing binary packages is finding out which package is the correct one.

3.1.1. Getting the Correct Package

The binary Squish packages are available in your Customer Area on the froglogic website. To find out which of these packages is the one you need, you first need to know whether you are going to test either a web application or an application written using the Qt® toolkit. Additionally, you need to know which operating system you are using, i.e. Linux, Mac OS X, or Microsoft Windows.

If you will be testing a Qt application, you need to collect some further technical information in order to be able to choose the correct package:

  1. Which version of Qt is used by the application you want to test?

  2. Which compiler (and which version of the compiler) was used to compile the Qt library (and the application which you want to test)?

If you don't know this yourself, it's likely that a developer will be able to give you this information. After you have collected this information, the following table can tell you the name of the package to be used for each edition/operating system/compiler/Qt version combination.

[Note]Note

Please note that should you be unable to find an entry in the table which matches your local setup, it is best that you build Squish from source. This ensures that it integrates correctly with your local software configuration. Building Squish from source is described in Installing from Source Packages (Section 3.2).

Table 3.1. Available binary packages for froglogic Squish

Available binary packages for froglogic Squish
Operating SystemEditionQt VersionCompilerPackage Name
Windows (32bit) Qt Testing 3.3.5 MinGW squish-3.1.0-qt335-win32-mingw.zip
Windows (32bit) Qt Testing 3.3.6 MinGW squish-3.1.0-qt336-win32-mingw.zip
Windows (32bit) Qt Testing 4.1.x MinGW squish-3.1.0-qt41x-win32-mingw.zip
Windows (32bit) Qt Testing 4.1.x MinGW squish-3.1.0-qt42x-win32-mingw.zip
Windows (32bit) Qt Testing 3.3.5 MSVC 6 squish-3.1.0-qt335-win32-msvc6.zip
Windows (32bit) Qt Testing 3.3.6 MSVC 6 squish-3.1.0-qt336-win32-msvc6.zip
Windows (32bit) Qt Testing 4.1.x MSVC 6 squish-3.1.0-qt41x-win32-msvc6.zip
Windows (32bit) Qt Testing 4.1.x MSVC 6 squish-3.1.0-qt42x-win32-msvc6.zip
Windows (32bit) Qt Testing 3.3.5 MSVC 7.1 (.NET 2003) squish-3.1.0-qt335-win32-msvc7.zip
Windows (32bit) Qt Testing 3.3.6 MSVC 7.1 (.NET 2003) squish-3.1.0-qt336-win32-msvc7.zip
Windows (32bit) Qt Testing 4.1.x MSVC 7.1 (.NET 2003) squish-3.1.0-qt41x-win32-msvc7.zip
Windows (32bit) Qt Testing 4.1.x MSVC 7.1 (.NET 2003) squish-3.1.0-qt42x-win32-msvc7.zip
Windows (32bit) Qt Testing 3.3.5 MSVC 8.0 (2005) squish-3.1.0-qt335-win32-msvc8.zip
Windows (32bit) Qt Testing 3.3.6 MSVC 8.0 (2005) squish-3.1.0-qt336-win32-msvc8.zip
Windows (32bit) Qt Testing 4.1.x MSVC 8.0 (2005) squish-3.1.0-qt41x-win32-msvc8.zip
Windows (32bit) Qt Testing 4.1.x MSVC 8.0 (2005) squish-3.1.0-qt42x-win32-msvc8.zip
Windows (64bit) Qt Testing 3.3.5 MSVC 8.0 (2005) squish-3.1.0-qt335-win64-msvc8.zip
Windows (64bit) Qt Testing 3.3.6 MSVC 8.0 (2005) squish-3.1.0-qt336-win64-msvc8.zip
Windows (64bit) Qt Testing 4.1.x MSVC 8.0 (2005) squish-3.1.0-qt41x-win64-msvc8.zip
Windows (64bit) Qt Testing 4.1.x MSVC 8.0 (2005) squish-3.1.0-qt42x-win64-msvc8.zip
Linux (32bit) Qt Testing 3.3.5 any squish-3.1.0-qt335-linux32.tar.gz
Linux (32bit) Qt Testing 3.3.6 any squish-3.1.0-qt336-linux32.tar.gz
Linux (32bit) Qt Testing 4.1.x any squish-3.1.0-qt41x-linux32.tar.gz
Linux (32bit) Qt Testing 4.1.x any squish-3.1.0-qt42x-linux32.tar.gz
Mac OS X (PPC) Qt Testing 3.3.5 GNU gcc 4.0 squish-3.1.0-qt335-macppc-gcc4.0.tar.gz
Mac OS X (PPC) Qt Testing 3.3.6 GNU gcc 4.0 squish-3.1.0-qt336-macppc-gcc4.0.tar.gz
Mac OS X (PPC) Qt Testing 4.1.x GNU gcc 4.0 squish-3.1.0-qt41x-macppc-gcc4.0.tar.gz
Mac OS X (PPC) Qt Testing 4.1.x GNU gcc 4.0 squish-3.1.0-qt42x-macppc-gcc4.0.tar.gz
Mac OS X (Intel) Qt Testing 3.3.5 GNU gcc 4.0 squish-3.1.0-qt335-maci386-gcc4.0.tar.gz
Mac OS X (Intel) Qt Testing 3.3.6 GNU gcc 4.0 squish-3.1.0-qt336-maci386-gcc4.0.tar.gz
Mac OS X (Intel) Qt Testing 4.1.x GNU gcc 4.0 squish-3.1.0-qt41x-maci386-gcc4.0.tar.gz
Mac OS X (Intel) Qt Testing 4.1.x GNU gcc 4.0 squish-3.1.0-qt42x-maci386-gcc4.0.tar.gz
Windows (32bit) Web Testing any any squish-3.1.0-web-win32.zip
Linux (32bit) Web Testing any any squish-3.1.0-web-linux32.tar.gz
Mac OS X (PPC and Intel) Web Testing any any squish-3.1.0-web-mac.tar.gz
Windows (32bit) Four J's GDC Testing 3.3.5 any squish-3.1.0-gdc-qt335-win32.zip
Windows (32bit) Four J's GDC Testing 3.3.6 any squish-3.1.0-gdc-qt336-win32.zip
Linux (32bit) Four J's GDC Testing 3.3.5 any squish-3.1.0-gdc-qt335-linux32.tar.gz
Linux (32bit) Four J's GDC Testing 3.3.6 any squish-3.1.0-gdc-qt336-linux32.tar.gz


[Note]Note

Squish binary packages do not require installion of any files into some additional directory of your computer, so the directory you choose for decompressing the package can just as well be the one from which you will run Squish.

After you have decided which of these packages is appropriate for you, download it onto your computer and decompress it somewhere. Decompressing these files requires a ZIP decompressor for Windows. The Linux and Mac OS X packages use GNU gzip and GNU tar. In case you don't have a graphical interface for your respective compressor, change to the directory into which you downloaded the package and then execute the following command:

On Windows

C:\squish> unzip -o <packagename>

On Linux

% tar zxf <packagename>

On Mac OS X

% tar zxf <packagename>

<packagename> is a placeholder for the actual name of your binary package, as given in the table above.

3.1.2. Configuring the Package

Before you can run Squish from a binary package, you need to run a special configuration tool contained within the package so that Squish knows where certain files reside on your hard disk. This configuration tool is called setup and is stored in the top-level directory of your package. Hence, after decompressing the package, you should be able to find an executable file called setup - start the configuration process by executing that program.

[Note]Note

In case you're using a binary package of Squish built for the Microsoft Visual Studio 2005 compiler (MSVC8), your system might lack certain runtime libraries. You can tell whether you lack them by starting the setup program: if it works, everything is fine. However, if you get an error message along the lines of “This application has failed to start because the application configuration is incorrect” then you have to install the required runtime libraries first. To do so, simply run the vcredist_x86 program which is in the same directory as the setup program prior to starting the setup.

[Note]Note

If you want to go back and change a setting you made during the configuration, you can use the button labeled Back to navigate back to the respective page, adjust your configuration, then move on again using the Next button.

3.1.2.1. Entering the License Key

A picture of the license key page from the froglogic Squish configuration program.

After acknowledging the welcome page, by pressing the button labeled Next on the bottom of the setup program, the next page will request you to enter your Squish license key as given to you by froglogic. If you already have a previous Squish installation on your computer, the license key used previously will be shown in the input field. Enter your license here exactly as given to you, including any dashes.

[Note]Note

Since the release of Squish 3.0 also introduced a new license key scheme, you should have received a new license key in your customer area on the froglogic website (called squish-3-license). In case your previous installation didn't already use this scheme, it is recommended that you use the new license key instead of any previous one, as used by Squish 1.x and 2.x.

Click the Next button to advance to the next step of the configuration process. If there are any problems with the license (for instance, if it has expired or is malformed) then a message box will be shown, notifying you of the issue.

3.1.2.2. Acknowledging the Terms of Use

A picture of the license test page from the froglogic Squish configuration program.

After entering your license key, you will be presented with the license under which you are permitted to use your copy of Squish. Please read the entire license text carefully before proceeding. Two buttons labeled Accept and Decline, below the license text, let you state whether you agree or disagree with these terms.

[Note]Note

The license text can change depending on which license key you entered.

Accepting the license text will allow you to click the Next button, so you can proceed to the next step of the configuration process.

3.1.2.3. Path to Qt Library

A picture of the page from the froglogic Squish configuration program where you configure which Qt library should be used for the tested application.
[Tip]Tip
This step is only necessary if you are configuring a Squish package set up for testing Qt applications and if your license key entitles you to test Qt applications. If either of these two conditions don't apply, you won't be presented with this page and can safely skip to the next section.

In order to be able to test Qt applications, you need to point Squish to the Qt library used by the application you intend to test. You can either enter the full path to the file into the input field, or click the button labeled Browse at the right of the input field. Clicking this will open a convenient file selection dialog, which lets you browse your files and select the library.

[Note]Note

If you don't know where the library is stored on your computer, your system administrator should be able to tell you.

After specifying the path to the requested Qt library, use the Next button to advance to the next step of the setup.

3.1.2.4. Paths for Java™ Settings

A picture of the page from the froglogic Squish configuration program where you configure the necessary Java paths.

In order to be able to test Java™ applications, you need to point Squish to the jre sub directory of your JavaSDK installation, or if you only have the JRE installed, the root of that installation.

If you also want to test Java™ applications based on the SWT GUI toolkit, then the path to the SWT jar file as well.

[Note]Note

Beware that the SWT jar file needs the accompanying shared libraries (or dll's) to be found in your system path.

[Note]Note

If you don't know where the library is stored on your computer, your system administrator should be able to tell you.

After specifying the path to the requested jre directory and optionally filled in a valid path to a SWT jar file, use the Next button to advance to the next step of the setup.

3.1.2.5. Preferred Scripting Language

A picture of the page from the froglogic Squish configuration program where you choose the scripting language that should be used by default.

Test scripts created with Squish can be formulated in a number of scripting languages, such as Python, Tcl or JavaScript. This page lets you define which language should be used by default when creating new test suites. Select your preferred scripting language here (or choose the default), then proceed to the next step using the Next button.

3.1.2.6. Preferred Web Browser

A picture of the page from the froglogic Squish configuration program where you choose the web browser that should be used when testing web applications.
[Tip]Tip
This step is only necessary if you are configuring a Squish package set up for testing Web applications on Linux, and if your license key entitles you to test Web applications. If this is not the case, you won't be presented with this page and can safely skip to the next section.

When using Squish to test web applications, it is necessary to decide which browser should be used for recording and replaying the tests. On Windows and Mac OS X, the default browser is used (Internet Explorer® and Safari® respectively). However, Linux systems have no default browser, and if more than one supported browser is detected you need to choose which browser should be used.

[Note]Note

If you are using a Linux package and there was just one supported browser found, it will be chosen silently and this page will be skipped.

Just select your preferred web browser, or choose the default selection, then move on with the setup by clicking the Next button.

3.1.2.7. Configuration Review

A picture of the configuration review page from the froglogic Squish configuration program.

All required information has now been gathered by the setup program and is presented here for you to review, an example of which is shown in the picture above. As usual, if you notice any mistakes, you can use the Back button of the setup program to go back to the respective page and adjust your choices, then return to the review page by using the Next buttons.

[Warning]Warning

Pressing the Next button on this page means that the configuration shown will be written out - a process which cannot be reversed (though you could re-run the setup program and overwrite the settings with new ones). Please ensure that the settings shown look sensible.

Proceeding to the next page, using the Next button, will save the configuration shown, and advance to the final page.

3.1.2.8. Concluding the Configuration

A picture of the final page from the froglogic Squish configuration program.

Congratulations! You have finished the installation, and all settings have been saved successfully. This page concludes the configuration of your Squish binary package.

You can now use the button labeled Finish to finish the installation and close the setup program. If you like, you can check any of the check boxes shown, should you subsequently want to open the Squish IDE or the Squish manual.

3.1.3. Using the Binary Package

After acquiring, decompressing and configuring your Squish binary package, you are ready to go. You can start the Squish IDE by navigating to the bin folder in the place where you unpacked your binary package, and then starting the program called squish.

If this is your first time using Squish, it might be a good idea to proceed to the tutorial so you can familiarize yourself with the software.

For testing a sample Qt application, see Tutorial: Creating the First Test with Squish for Qt (Chapter 6).

For testing a sample Tcl/tk application, see Tutorial: Creating the First Test with Squish for Tk (Chapter 8).

For testing a sample web application, see Tutorial: Creating the First Test with Squish for Web (Chapter 10).

For testing a sample GDC application, see Tutorial: Creating the First Test with Squish for GDC (Chapter 7).

For testing a sample Java™ application, see Tutorial: Creating the First Test with Squish/Java™ (Chapter 11).