Automating native or Qt (file) dialogs in Qt applications

Last edited on

In a nutshell

Dialogs in Qt applications

Qt applications running on Windows use the native Windows file dialogs by default. The native Windows file dialogs looks like this:

However, when a Qt application is run as an AUT in Squish (on Windows), the application may use Qt’s own dialogs (implemented using Qt GUI controls). The Qt 4/5 based file dialogs look like this:

As you can see the Qt based dialogs may look different from the native dialogs. (This also applies to the directory chooser dialogs.)

This means that Squish tries to force Qt to use Qt dialogs rather than native dialogs. This is done because:

Even though the dialogs look different, this should have no affect on your program. This is true for Qt dialogs on other platforms as well.

Note: On Windows (not Unix) it is possible to automate native Windows dialogs, too, but that requires an additional license for Squish for Windows, as well as a customized version of Squish. For more information, see Adding full support for “Windows” controls to Squish for Java, Qt, Web, etc.

Qt 4.x to 5.2 (incl.) & Qt 5.7 and higher

It is possible for Squish to try to force the use Qt dialogs over native ones, and Squish does so by default.

If for some reason, you wish to see native dialogs instead, you can edit the SQUISHDIR/etc/qtwrapper.ini entry for UseNativeDialogs and set it to 1.

Qt 5.3 to Qt 5.6

Qt 5.3 to Qt 5.6 do not allow Squish to disable native dialogs, which has a number of drawbacks:

Solutions

General solution #1 - Automate the dialogs via <code>nativeType()</code>

This solution does not allow for precise synchronization based on object existence, therefore the snooze() command must be used in addition to ensure that the dialog really is already on the screen and has input focus when starting to send key presses via nativeType().

For more details please see Automating file dialogs with type() and nativeType() .

General solution #2 - Request Qt based dialogs via parameter &ldquo;-platformtheme none&rdquo;

Adding the command line arguments -platformtheme none when starting the AUT may enable Qt based file dialogs. For example:

def main():
    startApplication("addressbook -platformtheme none")

The above will make Qt try to load a plug-in with the name “none” and since no such plug-in exists, it will fall back to its internal defaults.

This solution has been successfully tested on Linux/X11 and Windows using Qt 5.3.0 and it applies to the traditional QFileDialog as well as the new QML/QtQuick2 FileDialog.

Known issues with the solution:

General solution #3 - Request Qt based dialogs in application&rsquo;s source code itself

A Qt application can itself request Qt based dialogs through the QFileDialog.DontUseNativeDialog option which is passed as options to many of the QFileDialog static public functions, as well as through its own getter/setter.

This could be done optionally, based on the existence of the environment variable SQUISH_PREFIX, to limit this behavior to cases where the application is being started by Squish.