TestComplete supports testing of various Rogue Wave controls. You can also modify project properties so that TestComplete recognizes your custom Rogue Wave controls. The sections below describe how you can test Rogue Wave controls in detail.
About Supported Rogue Wave Controls
TestComplete can work with any Rogue Wave controls via a graphical user interface. Besides that, it provides extended support for some Rogue Wave grid controls. These controls are automatically associated with special program objects that extend the control’s functionality with a number of supplementary methods and properties. These extended methods and properties let you perform various operations over the controls, for example, simulate mouse clicks on grid cells, get and set cell values, and so on.
A license for TestComplete Desktop module.
The Rogue Wave Controls Support plugin. It provides access to controls via special program objects.
This plugin is installed and enabled automatically.
If you experience issues when working with the controls, select File | Install Extensions from the TestComplete main menu to check whether the plugin is active. If the plugin is not available, run the TestComplete installation in the Repair mode.
Below is the full list of the Rogue Wave controls for which TestComplete provides extended support.
Note that TestComplete provides support for the listed controls as well as for their descendants. However, to make this possible, you need to specify the class name of your inherited control in the corresponding group of the project’s Object Mapping options. For more information, see Object Mapping.
|Rogue Wave Stingray Objective Grid (.NET)
|Rogue Wave Stingray Objective Grid for .NET ver. 9.04
|Rogue Wave Stingray Objective Grid (C++)
|Rogue Wave Stingray Objective Grid ver. 10.04
Recognizing Custom Controls
To command TestComplete to recognize your custom Rogue Wave controls, open your project’s Object Mapping options and add the control’s class name to the corresponding subgroup of the Rogue Wave Controls group. The subgroup name corresponds to your custom control’s type. Once the control is mapped, it gets all the properties, methods and actions specific to the Rogue Wave control of the corresponding type.
If the specified custom control does not fit the control’s type, then it may not properly respond to commands that TestComplete sends, so recording or playing back user actions over the tested control will cause errors.