To test a Visual C++ (unmanaged) application with TestComplete, you need to compile your application with specific compiler options. This enables TestComplete to record and play back object-specific actions for Visual C++ UI controls, and lets you use native object methods and properties in your tests.
In This Section
Compiler Settings for Visual C++ 8.0 and Later Open Applications (Unmanaged Code)
Explains how to add debug information to an application created in Microsoft Visual Studio 2005 - 2017 so that your tests have access to all internal members of the application’s objects.
Compiler Settings for Visual C++ 7.x Open Applications (Unmanaged Code)
Explains how to add debug information to an application created in Microsoft Visual Studio .NET 2002 or 2003 so that your tests have access to all internal members of the application’s objects.
Compiler Settings for Visual C++ 6.0 Open Applications
Explains how to add debug information to an application created in Microsoft Visual C++ 6.0 so that your tests have access to all internal members of the application’s objects.
Compiler Settings for Visual C++ Open Applications Created With Intel C++
Explains how to add debug information to an application created with the Intel C++ compiler, so that your tests have access to all internal members of the application’s objects.
Preparing Rogue Wave Stingray Objective Grid (C++) Controls for Testing
Explains how to re-compile Rogue Wave Stingray Objective Grid components with debug information so that TestComplete gets access to such components in the tested Visual C++ application.
Downloading MFC Debug Information
Describes the prerequisites for automating MFC controls in Visual C++ applications that use MFC in a shared DLL.
Related Topics of Interest
Describes the specifics of Debug Info Agent™ that provides you with access to applications’ debug information.
Troubleshooting Visual C++ Applications
Describes possible problems that may occur when testing Visual C++ applications and possible solutions to these problems.