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:
An active license for the TestComplete Desktop module.
The following plugins must be enabled in TestComplete:
Qt Applications Support
Qt Controls Support
These plugins are installed and enabled automatically when you install TestComplete. You can check if these plugins are active in the File > Install Extensions dialog of TestComplete.
Qt application modules
Do not rename or modify the following modules of the tested Qt application:
Where N is the used Qt version.
TestComplete uses these modules to access objects in the Qt applications. If these modules are renamed or some functions are deleted from these modules, TestComplete will not be able to access objects in tested 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.