Known Issues - Squish 9.2.0 Release¶
(Known Issues of previous / next version)
Release Date: February 10th, 2026
Recommended Update: 9.2.1
Commandline test execution with squishrunner will not inform the user when there is no license seat available on the QLS server¶
When all test execution license seats on the QLS server are occupied, starting another test run on the commandline using squishrunner will leave that execution hanging until a seat becomes available. The squishrunner output will not indicate that it is waiting for a license seat becoming available and it will not terminate the execution itself.
Workaround
If necessary, contact the license manager who can check whether the QLS server instance has any available licenses, and whether this is the cause of the squishrunner hanging.
IDE misbehaves when the QLS server connection is disrupted¶
Recording aborts when creating a verification while the QLS server connection is disrupted¶
When the connection between the user system and the QLS server is disrupted
while attempting to create a Verification from the Controlbar then the recording
session will be aborted. The IDE returns to its Test Management perspective
but subsequent test execution or recordings will not be possible. After some
time the IDE will open the License Dialog, if the connection is not
re-established, informing the user about the problem. Fixing the connection
problem and closing the dialog will not fix the problems with running or
recording tests.
Workaround
Terminate the IDE after it aborted the recording. Repair the connection and then start the IDE again.
Recording aborts when adding an image-based interaction or verification while the QLS server connection is disrupted¶
When the connection between the user system and the QLS server is disrupted
while attempting to create an image- or OCR-based Interaction or Verification
from the Controlbar (Insert -> mouseClick (\<Image\>)) then the recording
session will be aborted. The IDE returns to its Test Management perspective but
subsequent test execution or recordings will not be possible. After some time
the IDE will open the License Dialog, if the connection is not re-established,
informing the user about the problem. Fixing the connection problem and closing
the dialog will not fix the problems with running or recording tests.
Workaround
Terminate the IDE after it aborted the recording. Repair the connection and then start the IDE again.
Recording snippets at a breakpoint fails to work when QLS server connection is disrupted¶
When the connection between the users system and the QLS server is disrupted
while attempting to begin a snippet recording at a test execution breakpoint
then the IDE will show the License Dialog informing the user about the
connection problem. Fixing the connection problem and closing the License Dialog
will not start the recording and starting it via the toolbar button is
not possible either. This situation can also occur when an object not found or
image not found dialog appears due to a lookup error and the user selects the
Debug option in the dialog
Workaround
Terminate the IDE, making sure there are no leftover processes via Task Manager (squishrunner or squishserver). Afterwards repair the connection to the QLS server and start the IDE again.
Creating a new testsuite lacks GUI toolkit options when the QLS server connection is disrupted¶
When the connection between the users system and the QLS server is disrupted and
the user start creating a new testsuite then the IDE opens the License Dialog
to inform the user about the connection problem. If the user fixes the connection problem
and closes the dialog the testsuite wizard does not list any toolkits for selection
and the suite creation cannot continue. The testsuite wizard shows the
following error instead:
"Could not find any GUI toolkits. Please check your license key and the Squish
Tools installation.".
Workaround
Abort the testsuite wizard and open it again.
The license dialog is not shown when Squish attemps to launch an AUT while the QLS server connection is disrupted¶
When the connection between the users system and the QLS server is disrupted
while the user selects the AUT to record or launch in the Launch Settings
dialog, then the launching of the application will fail with an
error. However the IDE will not open the license dialog to help the user fix a
potential problem with the license configuration. It only produces a
corresponding error message in the Runner/Server Log view. The same problem
occurs when using an attachable AUT instead of letting Squish launch an AUT for
inspection or recording.
Workaround
When the cause of the issue is the network connection itself that issue needs to be fixed and the IDE can then be used normally again. In case the QLS server configuration needs to be adjusted the dialog can be opened from the Help menu manually.
IDE windows disappear in rare cases when starting a recording while the QLS server connection is disrupted¶
When the connection between the users system and the QLS server is disrupted
when starting to record a script snippet the recording will be aborted, the
License Dialog will be shown and forces the user to fix the connection problem
before allowing to continue using the IDE. A subsequent attempt to start the
snippet recording functionality may lead to the IDE to hide all its UI and make
it impossible to interact with this.
Workaround
We advise to restart the IDE when the License Dialog is shown the first time
in this scenario and not attempt to start the snippet recording after fixing
the connection problem.
If the IDE UI has already vanished and the AUT has been launched - or attached to - then terminating the AUT will bring back the IDE UI and allow to restart it.
Using Remote Control functionality while running a script when the QLS server connection is disrupted¶
When the connection between the users system and the QLS server is disrupted
and the IDE is set up to open the Remote Control view during test execution,
then the IDE may disappear completely in rare case when starting a test
execution. The IDE will briefly show the License Dialog and then hide its main
window but will not open the Controlbar either.
Workaround
Use the Task Manager of the system to find the Squish IDE process and forcefully terminate it as well as any child processes. Start the IDE again.
Squish for MCUs¶
Problems with detecting, flashing, and resetting Infineon Traveo II MCU devices on Linux¶
Starting with Squish 9.2.0, automated testing of applications written with Qt Quick Ultralite 2.12 or newer
is possible on Infineon Traveo II MCU devices. On some Linux distributions, additional permissions
(access to USB and serial port) need to be set to prepare the MCU device for testing with Squish. Without these
permissions, the device will be detected only as a generic UART device by the Squish IDE (if detected correctly,
the device identifier will contain kitprog3 string). Consequently, flashing and resetting the device
will fail. This failure is usually visible in squishrunner log as Raw UART connection cannot flash a new image to the device
or Raw UART connection cannot reset the device.
The easiest way to set the right permissions to access USB and serial port is to use vendor-provided
udev rules. These can be found in a file called .*-openocd.rules that is usually part of recommended
vendor tools package
(for Infineon: Auto Flash Utility
or Infineon OpenOCD). OpenOCD's
readme
outlines in Permission Delegation
section how to use these rules to configure the correct permissions on any Linux host.
Squish Installer¶
Installation folder not removed after uninstallation on Windows¶
In some cases on Windows, the Squish installation folder might not get completely removed during uninstalation.
The file <squish_installation>\qls\service\logs\qtlicd.log might be locked by the running QLS service process,
and thus cannot be removed. Also, because of this, the parent folders cannot be removed either.
The issue will be addressed in the next Squish release.
Workaround
Use the Windows Task Manager to forcefully terminate the process qtlicd.exe (Qt License Service), and then manually remove the installation folder.
Alternatively, you can also restart your computer, and then manually remove the installation folder.