TestComplete can recognize Developer Express CheckEdit controls in .NET applications. It provides special properties and methods that let you retrieve the controls data and simulate user actions on the controls (see below).
Supported component versions: Developer Express XtraEditors ver. 7.2, 8.2 - 10.2, 11.2, 12.1 - 18.1.3, 19.1.3, 20.1.6, 21.1.3.
In order for TestComplete to be able to work with Developer Express CheckEdit controls, the following requirements must be met:
You must have an active license for the TestComplete Desktop module.
The control’s class name must be specified in the Developer Express Controls | WinForms | CheckEdit group of your project’s Object Mapping options. By default, this group contains the following item:
You can also command the test engine to recognize custom controls as Developer Express CheckEdit controls. See below for information about this.
Support for the Developer Express CheckEdit controls is implemented by the Developer Express Control Support plugin. 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 and check whether the plugin is active. (You can find the plugin in the Common group.) If the plugin is not available, run the TestComplete installation in the Repair mode.
Recognizing Custom Controls
To command TestComplete to recognize your custom controls as Developer Express CheckEdit controls:
Open your project’s Object Mapping options.
Add the control’s class name to the Developer Express Controls | WinForms | CheckEdit group.
If you do not know the control’s name, you can ask the control’s developers, or you can view the control’s
ClrFullClassNameproperty in the Object Browser panel. As an alternative, you can click Add From Screen and select your custom control on screen. TestComplete will retrieve the control’s class name and add it to the selected mapping group automatically. For detailed information, see Object Mapping.
Once the control is mapped, it gets all the properties, methods and actions specific to the Developer Express CheckEdit control.
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.
When testing Developer Express CheckEdit controls, you can use properties and methods specific to these controls, as well as properties and methods that TestComplete applies to tested objects, onscreen objects and window objects. For the full list of available properties and methods, see the following topics: