TestComplete supports testing of various Xceed controls. You can also modify project properties so that TestComplete recognizes your custom Xceed controls. The sections below describe how you can test Xceed controls in detail.
About Supported Xceed Controls
TestComplete can work with any Xceed controls via a graphical user interface. Besides that, it provides extended support for Xceed Grid controls. These controls are automatically associated with
XceedDotNetGrid 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 control, for example, simulate mouse clicks on grid cells, get and set cell values, and so on.
A license for the TestComplete Desktop module.
The Xceed Control Support plugin. This plugin provides access to Xceed Grid controls via special program objects and enables creating of table checkpoints for them.
This plugin is installed and enabled automatically as part of the TestComplete Desktop module.
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 Xceed 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.
|Xceed GridControl||Xceed Grid for .NET ver. 2.2 - 3.9||Xceed.Grid.GridControl|
Recognizing Custom Controls
To command TestComplete to recognize your custom Xceed controls, open your project’s Object Mapping options and add the control’s class name to the corresponding subgroup of the Xceed 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 Xceed 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.