Document toolboxDocument toolbox

A new version of Qualitia Automation Studio for Web and Mobile 7.2.x is now available. We highly recommend you upgrade. Find more details here.

MobileText Actions

Owned by Sagar Dubewar (Unlicensed)
Last updated: Mar 02, 2018

Set

This action sets the text into mobile text box object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Value

Enter the value you want to add into specified mobile text box.

No

String

Example:

Set                        "Qualitia"

StoreText

This action reads the existing text available in mobile text box and stores it into the specified key. 

Input Parameters:

ParameterName

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the text.

Yes

String


Example:

StoreText                       "Key"

On this page:

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

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.

(warning) Use this parameter with caution only when control on swipe speed is required.

No

String


Example:
Swipe                  "up"                   "10"             "1"

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 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", "type", "visible", "label", "enabled", "accessible", "rect", "frame", "accessibilityContainer", "wdName", "wdValue", "wdType", "wdVisible", "wdLabel", "wdEnabled", "wdAccessible", "wdRect", "wdFrame", "wdAccessibilityContainer"

Input Parameters:

ParameterName

Parameter Description

Mandatory

Data Type

Key

Variable in which the property value will be stored

Yes

 String

Property

Property/attribute name whose value needs to be stored in "Key". This can be any accessible property of Android/iOS native object.

Yes

 String


Example:
StorePropertyValue                            "key"                     "text"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameters 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.

Yes

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 parameters can be true or false.

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

Yes

String

Example:
VerifyExistence                      "True"

WaitForObject

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 Configuration Settings (Execution) window.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTime

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

Yes

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.

Yes

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,execution continues to the next steps.

Not finding what you need?