About Support
TestComplete can recognize Win32 Pager controls in Windows applications. It provides special properties and methods that let you retrieve the controls data and simulate user actions on the controls (see below).
Requirements
In order for TestComplete to be able to work with your controls as with Win32 Pager controls, the control’s class name must be specified in the Win32 Controls and Windows | Pager group of your project’s Object Mapping options. By default, this group contains the following items:
- *SysPager*
- *PageScroller*
| Note: | The asterisk (*) wildcards specify variable parts of class names. |
You can also command the test engine to recognize custom controls as Win32 Pager controls. See below for information about this.
Recognizing Custom Controls
To command TestComplete to recognize your custom controls as Win32 Pager controls:
-
Open your project’s Object Mapping options.
-
Add the control’s class name to the Win32 Controls and Windows | Pager group.
If you do not know the control’s name, you can ask the control’s developers, or you can view the control’s
WndClassproperty 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 Win32 Pager 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.
Members
When testing Win32 Pager 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:
Properties