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.

WebEdit Actions

Owned by Sagar Dubewar (Unlicensed)
Last updated: Jan 18, 2021 by ravi.chandran (Unlicensed)


Set

This action enters the specified value into the edit box.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strValue

Enter the value that needs to be added into the specified edit box. You can give the alphanumeric value to be entered into the edit box. 

Yes

String

Example:

Set                            "Qualitia"



ClearText

This action clears the text present in the specified text box.

This action does not have any parameter.

Example:

ClearText

SecureSet

This action enters the expected value into the specified edit box. The value set in the parameter is encrypted once the focus is moved for security purposes.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Text

Enter the test that needs to be entered in the specified text box in the specified format.
Format: Encrypt(<TEXT TO BE ADDED>)

Yes

String

Example:
SetSecure "Encrypt(Abc)"
When the focus is moved away from the parameter Qualitia will automatically encrypt the data ABC and result in a secured text like "vHpmlfI4R3PQkCN4sZnuqw==þNWE3ZDdkNjE3N2JmNDM2ODgxMzQwYWI1MTA3YWNjMDc="

On this page:

StoreText

This action stores the text entered in an edit box 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 under which you want to store the text.

Yes

String

Example:
StoreText                   "textKey"

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"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameters can be true or false.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.

Yes

String

Example:
VerifyVisibility                      "True"

Click

This action clicks the specified object.

This action does not have any parameter.

Example:
Click

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"

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 

Example:
SetFocus

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"

ClickAt

This action clicks at the specified point on the object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

Yes

String

Y

The y-coordinate of the click.

Yes

String

Example
ClickAt        "5"            "10"

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.

ClickAndWait

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:
ClickAndWait

Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

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"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:

StoreChildCount                               "Key"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:

ClickJS

ActionClick

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver “Action” class to perform click action. Qualitia recommends using this action for web applications.

Example:

ActionClick

 

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text before exhausting timeout. 

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. Stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to show in the report in case the expected condition is not satisfied. value for this parameter can be Pass, Fail, and Defect.

No

String

Example:
WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

Not finding what you need?