MobileLink description properties

The MobileLink test object supports the description properties listed in the table below.

This test object is used for web link controls in an iOS mobile hybrid application that was not signed with a Developer certificate.

Note: Most object description properties can be used in the object repository description, in programmatic descriptions, in checkpoint and output value steps, and as argument values for the GetTOProperty and GetROProperty methods. However, some object description properties can be used only in checkpoint and output value steps, and with GetROProperty, WaitProperty, and CheckProperty steps, whereas others can be used only when identifying an object, as indicated below.

Property Name

Description

accessibilityid

The accessibility ID of the mobile control.

ChildObjects: Supported

bottom

The offset (in pixels) of the mobile control's bottom border from the top of the device's screen.

ChildObjects: Not supported

class*

The test object class name used by Digital Lab (UFT Mobile) to identify objects, such as button or table.

ChildObjects: Supported

container

The x-path to the control within its container.

Syntax: <Class>[index][row][cell] (All values are 0-based)

Example: Table[1][3][5] means that the object is in the 6th cell of the 4th row of the 2nd Table object.

ChildObjects: Not supported

height**

The mobile object's height (in pixels).

ChildObjects: Not supported

hint

Instruction or example indicating the type of content to enter for the value of a control, for example, a grayed out hint inside a text box.

isCheckable

Indicates whether the mobile control contains a check box that can be selected. Boolean value. (Relevant for controls with a check box.)

ChildObjects: Supported

isChecked

Indicates whether the mobile control is checked. Boolean value. (Relevant for controls with a check box.)

isClickable

Indicates whether the mobile control can be tapped (clicked). Boolean value.

ChildObjects: Not supported

isEnabled

Indicates whether the mobile control is enabled. Boolean value.

ChildObjects: Supported

isFocusable

Indicates whether the mobile control can be brought into focus. Boolean value.

ChildObjects: Supported

isFocused

Indicates whether the mobile control is in focus. Boolean value.

ChildObjects: Supported

left**

The offset (in pixels) of the mobile control's left border from the left side of the device's screen.

ChildObjects: Not supported

mcindex

An ordinal number assigned to the object by Digital Lab (UFT Mobile) to indicate the order in which the object appears on the device relative to other objects with an otherwise identical description.

ChildObjects: Supported

nativeclass

The native class of the mobile control.

ChildObjects: supported

resourceid

The resource ID for the control. (Relevant only for Android)

Object identification: Supported

right**

The offset (in pixels) of the mobile control's right border from the left side of the device's screen.

ChildObjects: Not supported

text

The text property of the mobile control.

ChildObjects: Supported

top**

The offset (in pixels) of the mobile control's top border from the top of the device's screen.

ChildObjects: Not supported

visual relations

Represents the test object's visual relations identifier.

Use this property in GetTOProperty and SetTOProperty steps to return or apply a VisualRelationsCollection object for a test object. The VisualRelationsCollection object enables you to retrieve or replace the visual relation identifier settings of a test object during a run session.

Syntax:

SetVRIColl = TestObject.GetTOProperty("visual relations")

TestObject.SetTOProperty "visual relations", VRIColl

For details, see VisualRelationsCollection Object in the Utility section of the Micro Focus UFT One Object Model Reference for GUI Testing.

This property is not listed in the Object Spy. It is not retrieved when you use the GetTOProperties method. It cannot be used in the Object Identification dialog box, the description area of the object repository, checkpoint or output value steps, and so on.

width**

The mobile object's width in pixels.

This property is not supported for object identification.

ChildObjects: Not supported

* Required by Digital Lab (UFT Mobile) to identify the objects in the application.

** When defining the location of an object:

  • For native apps, use top, left, right, and bottom to define the location of the object on the device.

  • For native and hybrid apps, use abs_x, abs_y, width, and height to define the location of the object on the desktop screen, such as on the Digital Lab (UFT Mobile) remote access window.

Back to top

See also: