TestComplete recognizes any .NET application as an Open Application by default. This means that all native methods and properties of the application objects are available to the TC scripts. Stingray controls are not standard, therefore, you can work with them only using their own methods and properties. Since TestComplete provides you with the access to all of the native methods and properties of any .NET object, you can create a script that works with any custom .NET control. We already have a number of sample scripts that demonstrate how to work with different .NET grids (including the Stingray Objective Grid). You can find the samples on our Web site: http://www.automatedqa.com/products/...e/tc_grids.asp
If your tested application is an unmanaged C++ application which uses the Stingray components for Win32 applications, compiling it as Open won't provide TestComplete with the access to the native methods and properties of the Stingray controls since they are not implemented on the basis of the ATL, WTL or MFC frameworks. Therefore, you have to choose one of the following approaches:
- Make your application Connected and test the custom controls from the application code. Please see the 'Connected Applications' and 'Creating Connected Applications in C++' help topics for details.
- Create special helper functions in the application under test that will provide access to the controls. These helper functions should be implemented as methods of a window object (e.g. the form class) to be visible to TestComplete. TestComplete will be able to call these functions from scripts and, therefore, work with the custom controls.