In most cases, nothing special needs to be done to make an application testable, since the toolkit's API (e.g., Qt) provides enough functionality to implement and record test scripts. The connection to the squishserver is also established automatically, when the Squish IDE starts the AUT.

In some fairly rare situations it might be convenient for a test script to be able to access the API provided by the AUT or its components. This is possible and the necessary techniques are explained in the User Guide—How to Create and Access Application Bindings (Section 15.8).

Note

Throughout the manual, we often refer to the squish directory. This means the directory where Squish is installed, which might be C:\Squish, /usr/local/squish, /opt/local/squish, or somewhere else, depending on where you installed it. The exact location doesn't matter, so long as you mentally translate the squish directory to whatever the directory really is when you see paths and filenames in this manual.