Glossary

AUT

This is the Application Under Test, that is, the application that is to be tested by Squish

Application Bindings

See Wrapper.

Bindings

See Wrapper.

Record and Insert

This is the process whereby Squish executes an AUT and records the user's interactions with it and inserts the recorded script inside the current test case's script—thus extending the existing script. See also Run and Record.

OCR

Optical Character Recognition - In Squish's case, using an external program to analyze pixel image data and recognize text in it.

Run and Record

This is the process whereby Squish executes an AUT and records the user's interactions with it into a test script (which can then be edited and played back later). See also Record and Insert.

SquishRunner

The process that reads and writes test scripts, and writes test results. It communicates with the SquishServer and the AUT using TCP/IP.

SquishServer

The process that starts and stops the AUT or browser, and establishes a communication hook for SquishRunner to use. Also used for attaching to running AUT, possibly on a remote machine, and started with start*aut.

SQUISHDIR

This is the directory where Squish is installed on your system.

Squish User Settings Directory

This is the directory where Squish reads and writes its user settings. By default, it is %APPDATA%\froglogic\Squish on Windows and ~/.squish on other systems. It can be changed by setting the SQUISH_USER_SETTINGS_DIR environment variable.

Synchronization

Using a waitFor* function to tell Squish to wait until a certain object or item is ready. Or using a snooze() function. Generally, these are things that slow down the execution of Squish's test runner, to allow the AUT to catch up to it.

Wrapper

A wrapper is a function or class through which it is possible to access another function or class (the wrapped function or class). Synonymous terms are application bindings, and plain bindings.

For example, Squish has a whole set of wrapper functions and classes that make toolkit functions and classes accessible in test scripts. It is also possible to create custom wrappers to make AUT-specific functions and classes scriptable, although this is rarely necessary since Squish 4 creates such wrappers automatically. (See How to Create and Access Application Bindings.)