MobileCheckBox description properties

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

This object is supported in Android only.

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.

Name

Description

accessibilityid

The accessibility ID of the mobile control.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: 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

ChildObjects: Not supported

class*

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: Supported

height**

The mobile object's height (in pixels).

Object identification: Not supported

Checkpoints / Output value properties / GetROProperty: Supported

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.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: Supported

Android: Packaged apps only

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

ChildObjects: 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

ChildObjects: Supported

isclickable

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: Supported

isenabled

Indicates whether the mobile control is enabled. Boolean value.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: Supported

isfocusable

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: Supported

isfocused

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: 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

ChildObjects: Not supported

mcindex

An ordinal number assigned to the object by Digital Lab 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 for GetProperty for non-packaged apps

ChildObjects: Supported

nativeclass

The native class of the mobile control.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Android supported for Packaged apps only

ChildObjects: Android supported for packaged apps only

resourceid

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

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: 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

ChildObjects: Not supported

text

The text property of the mobile control.

Object identification: Supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: 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

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 OpenText Functional Testing 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.

Object identification: Not supported

Checkpoints / Output value properties / GetROProperty: Supported

ChildObjects: Not supported

* Required by Digital Lab 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 remote access window.

See also: