You can test your C++Builder applications without any specific preparations.

However, in some cases, you may need to perform preliminary operations to get better access to your application’s internals:

To get access to public, protected and private properties and methods of your C++Builder applications, compile your application with debug information. See —

Preparing C++Builder XE2 - XE8 and 10 Applications for Testing

Preparing C++Builder XE Applications With Debug Information

Preparing C++Builder 2009 - 2010 Applications for Testing

Preparing C++Builder 2007 Applications for Testing

Preparing C++Builder 2006 Applications for Testing

Preparing C++Builder 6 Applications for Testing

Note:

TestLeft test engine is incompatible with tools that change debug information format (for example, EurekaLog). We recommend that you disable such tools when compiling an application aimed for automated testing with TestLeft.

To test Developer Express VCL controls in your C++ Builder application and access their internals, prepare the control for testing. See —

Preparing Developer Express VCL Components for C++Builder Applications
To test TMS Software VCL controls in your C++Builder application and recognize the controls properly, compile the controls with full debug information. See —

Preparing TMS Software VCL Components for C++Builder Applications

When You Need to Prepare C++Builder Applications

See Also