7.6. Squish Initialization Files

Table of Contents

7.6.1. .ini Files
7.6.2. ignoredauts.txt

7.6.1. .ini Files

Squish uses some .ini files to control some aspects of the command line tools and the IDE's behavior. In general these files should not be edited; instead use the Squish IDE and Environment Variables (Section 7.5) to change any settings.

The .ini files include ide.ini, paths.ini, and server.ini. These files are stored in the %APPDATA%\froglogic\Squish\ver1 folder on Windows and the $HOME/.squish/ver1 directory on Unix-like systems such as Linux. In addition, for Squish for Qt editions there is a file called qtwrapper.ini which is stored in the SQUISHDIR/etc directory.

[Note]Squish for Qt for Windows-specific

If you are testing Qt applications on Windows that are not deployed or tested on other platforms you can force Squish to use native Windows dialogs rather than Qt dialogs (e.g., for opening files and for printing). To do this edit the qtwrapper.ini file (which may have to be created and put in the SQUISHDIR/etc directory mentioned above) using a plain text editor and add a new line to the General group's entry (creating a General group if necessary) so that you have:

[General]
UseNativeDialogs = 1

With this in place, Squish will use native dialogs when running Qt applications on Windows. Note that this should not be done for applications that are to be tested cross-platform with the same Squish tests.

7.6.1.1. paths.ini

The paths.ini file is used to store various paths—for example, where global scripts are stored. In the case of global scripts (which are stored under key “GlobalScriptDirs”), when using the findFile function to find a script file to pass to the source function, findFile first looks in the test case's scripts directory, then in the test suite's shared scripts directory, then in the paths listed in the paths.ini file, and finally in the directories listed in the SQUISH_SCRIPT_DIR environment variable. (The search stops as soon as the file is found.) The paths.ini file shouldn't need to be hand edited (see the Global Scripts view (Section 8.2.7)), but if you move your Squish setup to another system you will want to copy this file—assuming that you use the same paths of course.

7.6.1.2. squish.ini

The squish.ini file is used to store some important Squish settings, so it should be edited with care.

One of the file's General section entry's keys is Wrappers/Qt/InitScripts, and its value is a comma-separated list of Tcl files used to initialize Squish for Qt (no matter what scripting language is used for Qt tests). If you would like to enable or disable event compression (e.g., enable to combine lots of small mouse moves into a single mouse move) you can do so by adding a new Tcl file to this entry's list called eventcompression.tcl. This file should contain one or more lines such as this:

Tcl
enableEventCompression GLWidget false

Here, event compression for GLWidgets has been switched off. You can have as many lines of this form as you like so long as each one has the same format with the second word being the name of the relevant class and the third word being true or false.

7.6.2. ignoredauts.txt

Squish for macOS, and Unix versions of Squish for Qt, Squish for Tk, and Squish for Xview, read a file at startup, SQUISHDIR/etc/ignoredauts.txt, if it exists. The file is a list of process names, one per line. On Linux each process name is the same name as the executable binary file; on other systems it is the name used by the ps or top programs. Squish will not hook into any process listed in this file. This blacklist exists to provide a last resort means of stopping Squish from hooking into a sub-processes launched by an AUT that would be adversely affected by an attempt to hook into it—for example, it might terminate prematurely. If you have a problem with hooking into a sub-process it is best to contact froglogic's technical support for advice before editing this file.