Requirements for Testing C++Builder Applications

Applies to TestComplete 15.64, last modified on May 16, 2024

This topic describes requirements that should be met in order for TestComplete to be able to test C++Builder applications properly. If something goes wrong, check the requirements listed in the following sections:

C++Builder Support Plugins

Core C++Builder Plugin

TestComplete support for testing C++Builder applications is provided by the following plugins:

  • Delphi and C++Builder Application Support

  • Open Applications

  • Desktop Testing

These plugins are installed and enabled automatically. Therefore, you can test most C++Builder 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 VCL Controls Automation

The TestComplete Desktop module also includes pre-installed plugins for automated testing of standard and third-party C++Builder VCL controls. These plugins provide test objects, methods and properties for automating various operations on C++Builder VCL controls, getting their contents, state and so on.

Just like core support plugins, these plugins are also installed and enabled automatically.

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.

Note: Support for VCL controls that are wrappers over standard Win32 controls (such as TButton, TListBox, TTreeView and others) is built into TestComplete.

Compiling Notes

If you want to get access to public, protected and private properties and methods of your C++Builder application from your tests, you must compile your application with debug information. In TestComplete access to these internal members is provided by the Debug Info Agent™ which is enabled by default.

Tip: If necessary, you can check whether the Debug Info Agent™ is enabled on the Project Properties - Debug Agent Options or Default Project Properties - Debug Agent Options page.

If your application is compiled with runtime packages, you must enable the Read debug information for statically linked libraries project option, otherwise TestComplete will be unable to get access to some of the application’s internals.

The Note for users of tools that may change debug information format: TestComplete Debug Info Agent is incompatible with tools that change the debug information format. An example of such a tool is EurekaLog 7. We recommend that you disable EurekaLog when compiling an application aimed for automated testing with TestComplete. Otherwise, TestComplete will not be able to access private, protected and public methods and properties of your C++Builder applications from your tests.

Testing C++Builder Applications Running Under Another User Account

To test C++Builder 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.

See Also

Testing C++Builder Applications
Supported Controls
Installing Extensions

Highlight search results