MobileWebElement description properties

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

This object is supported only when working with Mobile Center versions 1.5 and earlier.

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.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

bottom

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

class*

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not 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.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

domid

The DOM id property of the web control (in a hybrid application)

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

dominnertext

The DOM inner text property of the web control (in an hybrid application)

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

domname

The DOM name property of the web control (in a hybrid application)

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

domtitle

The DOM title property of the web control (in a hybrid application)

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

domxpath*

XPATH to the DOM element represented by the web control (in a hybrid application)

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

height**

The mobile object's height (in pixels).

Object identification: Not supported

Checkpoints / Output value properties / GetROProperty: 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.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

ischeckable

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ischecked

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

isclickable

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

isenabled

Indicates whether the mobile control is enabled. Boolean value.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

isfocusable

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

isfocused

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

left**

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

mcindex

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

nativeclass

The native class of the mobile control.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

resourceid

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Not supported

right**

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

text

The text property of the mobile control.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

top**

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

width**

The mobile object's width in pixels.

Object identification: Not supported

Checkpoints / Output value properties / GetROProperty: Supported

Example: * Required by UFT Mobile to identify the objects in the application.

Back to top

** 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 UFT Mobile remote access window.

Note: To change descriptions of Mobile test objects created in UFT One 12.02 Patch 1 (Mobile Center 1.01) or earlier, first update the test object in the object repository.

See also: