QAS Mobile Element Actions

Click

This action clicks the specified object.

This action does not have any parameter.

Example:

Click

LongPress

This action performs the long press event on the specified object.

This action does not have any parameter.

Example:

LongPress

NoOps

This action works as a placeholder. You can use this action as a reminder of something you want to perform later.

Example:

NoOps

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the existence's Boolean value will be stored.

Stores True if the object exists.
Stores False if the object does not exist.

Yes

String

Example:

StoreExistence "Key"

StorePropertyValue

This action stores the property of the specified object under the key name. The stored key value can be retrieved using the key name.

Some Android and iOS properties are not accessible.

List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"

List of accessible properties for iOS: "name", "value", "label", "hint"

Input Parameters:

ParameterName	Parameter Description	Mandatory	Data Type
Key	Enter the key name under which the property value will be stored.	Yes	String
Property	Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.	Yes	String

Example: StorePropertyValue "key" "text"

StoreVisibility

This action stores visibility of the mobile object under the specified key. The key value can be retrieved using the key name.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

The visibility value for the mobile object is stored as:

True denotes the object is visible
False denotes the object is not visible

No

String

Example:
StoreVisibility "Key"

Swipe

This action performs swipe and finds object until timeout occurs.

Input Parameters:

ParameterName

Parameter Description

Mandatory

Data Type

upDownLeftRight

Enter the direction of swipe:

Up: Move finger from down to up on the device screen.
Down: Move finger from up to down on the device screen.
Left: Move finger from right to left on the device screen.
Right: Move finger from left to right on the device screen.

No

String

timeoutInSeconds

Enter the timeout in seconds.

No

String

swipePageInSeconds

Enter in how many seconds one page should be swiped. Default is 1 second.
Use this parameter with caution only when control on swipe speed is required.

No

String

Example:

Swipe "up" "10" "1"

VerifyEnability

This action verifies the enability of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

Set True if you want to verify that the object is enabled.
Set False if you want to verify that the object is disabled.
Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability "True"

VerifyExistence

This action verifies the existence of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Value for this parameter can be True or False.

Set True if you want to check the existence.
Set False if you want to check the non-existence.

No

String

Example: VerifyExistence "True"

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Note:

For the WaitFor actions to complete successfully, the specified object must exist.
Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

Set True if you want to check for the appearance of the object.
Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject "10" "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, execution continues to the next steps.

WaitForObject "15" "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.