|The information below concerns legacy mobile tests that work with mobile devices connected to the local computer. In new cloud-compatible mobile tests, the test engine recognizes controls by their accessibility info.|
TestComplete can recognize iOS page controls in iOS applications. It provides special properties and methods that let you retrieve the controls data and simulate user actions on the controls (see below).
A license for the TestComplete Mobile module.
The iOS Support plugin. 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 Repair mode.
Your tested iOS application, the devices and the computer where TestComplete runs must be configured in a special way as it is described in the topics of the Preparing Applications, Devices, and Test Computers for iOS Testing (Legacy) section.
The control’s class name must be specified in the group of your project’s Object Mapping options. By default, this group contains the following item:
To command TestComplete to recognize instances of the specified class’s descendants as iOS page controls, select the Derived Classes check box next to the control’s class name.
Recognizing Custom Controls
To command TestComplete to recognize your custom controls as iOS page controls:
Open your project’s Object Mapping options.
Add the control’s class name to the iOS Controls | Page control group.
If you do not know the control’s name, you can ask the control’s developers, or you can view the control’s
ObjectClassNameproperty 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 iOS page 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 iOS page 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: