This topic describes requirements that should be met in order for TestComplete to be able to test Qt applications properly. If something goes wrong, check the requirements listed in the following sections:
Qt Support Plugins
Core Qt Plugin
TestComplete support for testing Qt applications is provided by the following plugins:
Qt Application Support
These plugins are installed and enabled automatically. Therefore, you can test most Qt applications right out-of-box, without any additional configuration.
You can check to see if these plugins are active by selecting File | Install Extensions from the TestComplete main menu. If one of these plugins is not available, you need to run the TestComplete installation in the Repair mode. For more information about changing installed TestComplete features, see Installing Extensions.
To use these plugins, you must have a license for TestComplete Desktop module.
Plugins for Qt Controls Automation
The TestComplete Desktop module also includes a pre-installed plugin for automated testing of standard and third-party controls. This plugin provides test objects, methods and properties for automating various operations on Qt controls, getting their contents, state and so on.
Just like core Qt support plugins, this plugin is also installed and enabled automatically as part of the TestComplete Desktop module.
You can verify that these plugins are active using the File | Install Extensions dialog. To re-install the plugins, run the TestComplete installation in the Repair mode.
Naming Qt Application Modules
You must not rename or modify the following modules of the tested Qt application: Qt5Gui.dll, Qt5Core.dll and Qt5Widgets.dll. These libraries are used by TestComplete when it recognizes the application and its objects. If you rename or modify these files, TestComplete will fail to access them (or some functions defined in these modules) and you will not be able to access the tested application’s objects from a test. For more information on this, see Troubleshooting Qt Applications.
Getting Access to Protected and Private Qt Members
If you want to get access to protected and private properties and methods of your Qt application from your tests, the following requirements must be met:
Your application must be compiled with debug information. For a detailed description of compiler settings, see the Compiler Settings for Visual C++ 8.0 and Later Open Applications (Unmanaged Code) topic.
The Enable Debug Agent and Read debug information for statically linked libraries options must be enabled in the Project Properties - Debug Agent Options dialog.
Tip: Debug Info Agent™ is enabled by default.
If all the conditions are met, you can get access to protected and private properties and methods of your Qt application and address them from your tests.
Qt applications should be compiled in Microsoft Visual Studio 2010 or later.
Testing Qt Applications Running Under Another User Account
To test Qt applications that run under a different user account, you need to configure certain COM Security settings on the computer. For details, see Settings for Testing Open Applications in RunAs Mode.
In addition, TestComplete must be launched with administrator privileges.