I am using TestComplete 4.x to automate a product built on C++ builder 5. TestComplete is unable to recognize the objects as standard objects. So we planned to go for a build with debug info. Unfortunately, we are facing some problem in making a build with DEBUG INFO for all the static libraries used in the application.
Please provide me a solution to resolve the issue. Please let us know, is it possible for us to go without debug info for static libraries.
Well, since you are unable to access and recompile the libraries in question, why would you need access to their internal details?
The core of your product, if it is expecting to use a third party library, will not be able to black box test that library. This would be true no matter which automated tool you used.
I would reccommend getting the developers to compile their internal DLLs and LIBs with Debug Info, not just for TC, but for their own testing benefit. The other code that cannot be changed, well, it cannot be tested.
I doubt anyone in your organization will have a problem with that answer...
I recommend that you try solving this problem by using wrapper files that can be generated by the PRegister utility: You will be able to create wrappers only for those classes that you are insterested in. Wrapper files allow TestComplete to access public elements of the application's objects. Please refer to the following Help topic to learn more about how to create wrappers for Borland C++ Builder applications: "Adding Public Information to Delphi and C++Builder Open Applications".