Automation Guide Application testing Mobile testing Testing mobile applications iOS Automation

 Capturing iOS controls with the Interface Viewer

Capturing iOS controls with the Interface Viewer

The Interface Viewer looks for the presence, and displays the graphical user interface (GUI) of, available iOS devices.

Ensure that the following requirements are met:

• You are familiar with the Interface Viewer and the concepts involved in creating an interface (see The Interface Viewer for details).
• A connection between your iOS device and the host machine has been established.
• The re-signed application is active on your iOS device.

Do the following to capture interface entities/elements of the re-signed application running on your iOS device:

1. Launch the Interface Viewer.

2. The Viewer generally attempts to restore the last viewing session (whether with a device or host machine) it was used for. If it does not automatically display the GUI environment of the iOS device you wish to view, select View > Switch Device to switch to it.
   
   

   At this point, the Interface Viewer scans the host system for all available mobile devices. If the Viewer finds only one mobile device, it displays a GUI tree of the re-signed application for that device.

3. If more than one mobile device is found, the Viewer displays the Select device dialog box to allow you choose which mobile device to automate. In this dialog box, select a desired device, then click the Open button.
   
   

   The Interface Viewer displays the associated GUI tree (the UI environment for the AUT on the iOS device).

   Note:
   • Only one AUT can be automated at a time. Therefore only one application’s UI environment is displayed.
   • TestArchitect does not support capturing native iOS dialog boxes - that is, ones that, regardless of origin, are posted by the operating system rather than directly from the application. (An example of such a dialog box would be one displaying the message <app name> Would Like To Use Your Current Location, which originates from an application submitting a request to iOS, which then presents the popup.)

4. The processes for mapping iOS windows and GUI controls to interface entities and elements, naming items using TA name, and saving interface definitions are essentially the same as described in Capturing interface definitions and Naming interface elements.

• The Identify button .
• Container classes.
• Showing invisible windows.