(8.6.X) WebImage Actions

Click

This action clicks the specified object.

This action does not have any parameter.

Example:

Click

ClickAction

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

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.	No	String
Y	The y-coordinate of the click.	No	String

Example

ClickAt "5" "10"

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

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter.
When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL window. You must give the URL and 'isURLPatternString' parameters.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

No

String

isURLPatternString

Enter one of the following:

True: If you want to apply the regex pattern to URL.
False: If you do not want to apply the regex pattern to URL.

No

String

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage? lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

DoubleClick

This action double-clicks the specified web element.

This action does not have any parameter.

Example:

DoubleClick

DownloadFile

This action clicks the link/element that opens a download window, which is used to download the files. You need to handle the action externally as it does not wait until the file is downloaded.

Qualitia uses its internal mechanism to handle the Download File pop-up screen.

You can also use AutoIT to execute this action on Windows operating systems only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the Auto Install Path for an offline suite:

Open the Qualitia Offline Configuration Manager.
Select the Offline Suite and the associated execution profile.
Click Qualitia Settings > General > AutoIT Path.

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
folderPath	The path where the file is to be download. Please check Table 1 "Parameter Mandate" to validate in the situation where this parameter will be mandatory. In case the parameter Mandatory; the user should take care that the folder path exists. The action does not validates whether the folder exist	Yes	String
FileName	The filename of the downloadable file, to be given incase the user requires to give specific name and not depend on the default name of the file. In case, the file already exist, similar window like below will appear. Such windows are not handled by the action. Incase, the user does not provide this data, the action will pick the default file name available while download.	No	String

Example:

Example DownloadFile "C:/ProgramData" "Qualitia"

DragAndDropToOffset

This action drags and drops the specified web element at the specified location.

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
offsetX	Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.	No	String
offsetY	Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.	No	String

Example:

DragAndDropOffset "100" "500"

MouseDown

This action simulates left-click at the specified location on the screen.

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
X	The x-coordinate of the click.	No	String
Y	The y-coordinate of the click.	No	String

Example:

MouseDown "5" "10"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter.

Example:

MouseOver

MouseOverJs

This action simulates a mouse hovering over the specified object by using JavaScript.

This action does not have any parameter.

Example:

MouseOverJs

RightClick

This action right-clicks the specified object.

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
option	The context menu option number that needs to be clicked.	No	String

Example

RightClick "3"

Note: This will select the third option from the context menu.

MouseUp

This action simulates the event that occurs when the user releases the mouse button.

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
X	The x-coordinate of the click.	No	String
Y	The y-coordinate of the click.	No	String

Example

MouseUp "5" "10"

ScrollIntoView

This action scrolls to view the specified object.

This action does not have any parameter.

Example:

ScrollIntoView

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

Yes

Array

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key	Syntax
ZENKAKU_HANKAKU	_{~{ZENKAKU_HANKAKU~}}
UP	_~{UP~}
TAB	_~{TAB~}
SUBTRACT	_{~{SUNSTRACT~}}
SPACE	_~{SPACE~}
SHIFT	_~{SHIFT~}
SEPARATOR	_{~{SEPARATOR~}}
SEMICOLON	_{~{SEMICOLON~}}
RIGHTCLICK	_{~{CONTEXTCLICK~}}
RIGHT	_~{RIGHT~}
RETURN	_~{RETURN~}
PAUSE	_~{PAUSE~}
PAGE_UP	_{~{PAGE_UP~}}
PAGE_DOWN	_{~{PAGE_DOWN~}}
NUMPAD9	_~{NUMPAD9~}
NUMPAD8	_~{NUMPAD8~}
NUMPAD7	_~{NUMPAD7~}
NUMPAD6	_~{NUMPAD6~}
NUMPAD5	_~{NUMPAD5~}
NUMPAD4	_~{NUMPAD4~}
NUMPAD3	_~{NUMPAD3~}
NUMPAD2	_~{NUMPAD2~}
NUMPAD1	_~{NUMPAD1~}
NUMPAD0	_~{NUMPAD0~}
NULL	~{NULL~}
MULTIPLY	_~{MULTIPLY~}
META	_~{META~}
LEFT_SHIFT(SHIFT)	_{~{LEFT_SHIFT~}}
LEFT_CONTROL(CONTROL)	_{~{LEFT_CONTROL~}}
LEFT_ALT	_{~{LEFT_ALT~}}
LEFT	_~{LEFT~}
INSERT	_~{INSERT~}
HOME	_~{HOME~}
HELP	_~{HELP~}
F12	_~{F12~}
F11	_~{F11~}
F10	_~{F10~}
F9	_~{F9~}
F8	_~{F8~}
F7	_~{F7~}
F6	_~{F6~}
F5	_~{F5~}
F4	_~{F4~}
F3	_~{F3~}
F2	_~{F2~}
F1	_~{F1~}
ESCAPE	_~{ESCAPE~}
EQUALS	_~{EQUALS~}
ENTER	_~{ENTER~}
END	_~{END~}
DOWN	_~{DOWN~}
DOUBLECLICK	_{~{DOUBLECLICK~}}
DIVIDE	_~{DIVIDE~}
DELETE	_~{DELETE~}
DECIMAL	_~{DECIMAL~}
CONTROL	_~{CONTROL~}
COMMAND (META)	_~{COMMAND~}
CLICK	_~{CLICK~}
CLEAR	_~{CLEAR~}
CANCEL (Esc)	_~{CANCEL~}
BACK_SPACE	_{~{BACK_SPACE~}}
ARROW_UP	_{~{ARROW_UP~}}
ARROW_RIGHT	_{~{ARROW_RIGHT~}}
ARROW_LEFT	_{~{ARROW_LEFT~}}
ARROW_DOWN	_{~{ARROW_DOWN~}}
ALT	_~{ALT~}
ADD	_~{ADD~}

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter.

Example:

SetFocus

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Parameter Name	Parameter Description	Mandatory	Data Type
value	Enter the value to be added for the Value attribute.	Yes	String

Example:

SetValueAttribute "#ff0990"

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"

StoreCSSProperty

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

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
keyProperty	Enter the key name under which the property value will be stored.	Yes	String
property	Enter the property name whose value you want to store.	Yes	String

Example:

StoreCSSProperty "Key" "display"

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"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names.

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
keyXPosition	Enter the key name to store the height of the location of the object.	Yes	String
keyYPosition	Enter the key name to store the width of the location of the object.	Yes	String

Example:

StoreLocation "Height" "Width"

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:

Parameter Name	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"

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
keyXPosition	Enter the key name under which you want to store the height of the object.	Yes	String
keyYPosition	Enter the key name under which you want to store the width of the object.	Yes	String

Example:
StoreSize "Height" "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names.
Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
keyText	Enter the key name to store the text from the specified object.	Yes	String

Example:

StoreText "Key"

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Parameter Name	Parameter Description	Mandatory	Data Type
strKey	Enter a variable to store the data present in the "value" attribute for the object.	Yes	String

Example:
StoreValueAttribute "Key"

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"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or False.

Set True if you want to check the visibility.
Set False if you want to check the invisibility.
Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility "True"

StoreVisibility

This action stores the visibility status for a web element under the specified key name in the following conditions:

True: If the web element is visible.
False: If the web element is not visible.

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
strKey	Enter a variable to store the visibility status.	No	String

Example: StoreVisibility "Key"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

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
attributeName	Enter the attribute name whose value you want to check.	Yes	String
attributeValue	Enter the partial expected partial attribute value.	Yes	String
timeOut	Enter the timeout (in seconds) to wait for the expected value.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout.	No	String
keyAttributeValueContains	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:
WaitForAttributeContains "id" "we323es" "5" "500" "Key" "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

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
attributeName	Enter the attribute name whose value you want to check.	Yes	String
attributeValue	Enter the value which should not be there in the attribute value.	Yes	String
timeOut	Enter the timeout (in seconds) to wait for the value to change.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.	No	String
keyAttributeValue	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:
WaitForAttributeValueContains "id" "232waf" "5" "500" "Key" "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

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
attributeName	Enter the attribute name whose value you want to check.	Yes	String
attributeValue	Enter the value which should not be there in the attribute value.	Yes	String
timeOut	Enter the timeout (in seconds) to wait for the value to change.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout.	No	String
keyAttributeValueNotToBe	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:
WaitForAttributeNotToBe "id" "232waf" "5" "500" "Key" "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

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
attributeName	Enter the attribute name whose value you want to check.	Yes	String
timeOut	Enter the timeout (in seconds) to wait for the attribute value.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the attribute value before exhausting timeout.	No	String
keyAttributeValue	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:

WaitForAttributeNotToBeEmpty "id" "5" "500" "Key" "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

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
attributeName	Enter the attribute name whose value you want to check.	Yes	String
attributeValue	Enter the exact expected value.	Yes	String
timeOut	Enter the timeout (in seconds) to wait for the expected value.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout.	No	String
keyAttributeValue	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:

WaitForAttributeToBe "id" "232waf" "5" "500" "Key" "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.

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
attributeName	Enter the attribute name whose value you want to check.	Yes	String
timeOut	Enter the timeout (in seconds) to wait for the attribute value to be empty.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the attribute value before exhausting timeout.	No	String
keyAttributeValue	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:

WaitForAttributeToBeEmpty "id" "5" "500" "Key" "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

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
childLocatorType	Enter the locator type of the object whose child you want to check.	Yes	String
childLocatorValue	Enter the locator value of the child you want to check.	Yes	String
timeOut	Enter the timeout (in seconds) to wait for the elements to appear.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the objects before exhausting timeout.	No	String
keyExistence	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:

WaitForChildElement "id" "2" "5" "500" "Key" "Defect"

WaitForClickability

This action waits for the specified object to be clickable. You may specify the timeout and polling interval, if required.

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 timeout (in seconds) to wait for the object to be clickable.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the object clickability before exhausting timeout.	No	String
keyClickability	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:

WaitForClickability "5" "500" "Key" "Defect"

WaitForExistence

This action waits for the existence of the specified object. You may specify the timeout and polling interval, if required.

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 timeout (in seconds) to wait for the existence of the object.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the existence of the object before exhausting timeout.	No	String
keyExistence	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:

WaitForExistence "5" "500" "Key" "Defect"

WaitForInnerTextContains

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

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

WaitForInnerTextContains "Connect" "5" "500" "Key" "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required.

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
innerTextRegXPattern	Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.	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:

WaitForInnerTextMatchesPattern ".[My]text." "5" "500" "Key" "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required.

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
innerText	Enter the text which should not be there in the attribute value.	Yes	String
timeOut	Enter the timeout (in seconds) to wait for the inner text to disappear.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout.	No	String
keyInnerTextNotContains	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:

WaitForInnerTextNotContains "Connect" "5" "500" "Key" "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required.

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
innerText	Enter the text which should not be there in the object.	Yes	String
timeOut	Enter the timeout (in seconds) to wait for the text to change.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the expected text before exhausting timeout.	No	String
keyInnerTextNotToBe	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:

WaitForInnerTextNotToBe "Connect" "5" "500" "Key" "Defect"

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.

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
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"

WaitForInvisibility

This action waits for the object to invisible. You may specify the timeout and polling interval, if required.

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 timeout (in seconds) to wait for the object to go invisible.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the invisibility before exhausting timeout.	No	String
keyInvisibility	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:
WaitForInvisibility "5" "500" "Key" "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. You may specify the timeout and polling interval, if required.

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 timeout (in seconds) to wait for the object to become non clickable.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the clickability before exhausting timeout.	No	String
keyNonClickability	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:

WaitForNonClickability "5" "500" "Key" "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. You may specify the timeout and polling interval, if required.

Note:

The WaitForNonExistence action passes even if you specify an invalid XPath but with correct syntax. As per the default behavior, Qualitia Automation Studio assumes that the specified path is valid and the object does not exist. Hence it returns a pass result.

Input Parameters:

Parameter Name	Parameter Description	Mandatory	Data Type
timeOut	Enter the timeout (in seconds) to wait for the non existence of the object.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for non existence of the object before exhausting timeout.	No	String
keyNonExistence	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:

WaitForNonExistence "5" "500" "Key" "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

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
expectedNumOfElements	Enter the expected number of elements to wait for. Note: The default value is 1.	No	String
timeOut	Enter the timeout (in seconds) to wait for the number elements to appear.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the objects before exhausting timeout.	No	String
keyNumberOfElements	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:

WaitForNumberOfElementsToBe "2" "5" "500" "Key" "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

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
expectedNumOfElements	Enter the expected number of elements to wait for.	No	String
timeOut	Enter the timeout (in seconds) to wait for the number elements to appear.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the objects before exhausting timeout.	No	Integer
keyNumOfElementsLessThan	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:

WaitForNumberOfElementsToBeLessThan "2" "5" "500" "Key" "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

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
expectedNumOfElements	Enter the expected number of elements to wait for.	No	Integer
timeOut	Enter the timeout (in seconds) to wait for the number elements to appear.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the objects before exhausting timeout.	No	String
keyNumOfElementsLessThan	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:

WaitForNumberOfElementsToBeMoreThan "2" "5" "500" "Key" "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM.

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 timeout (in seconds) to wait for the value to be detached.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for existence of the element before exhausting timeout.	No	String
keyStatus	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:

WaitForStaleness "5" "500" "Key" "Defect"

WaitForVisibility

This action waits for the object to be visible. You may specify the timeout and polling interval, if required.

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 timeout (in seconds) to wait for the object visibility.	No	String
pollingInterval	Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.	No	String
keyVisibility	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:

WaitForVisibility "5" "500" "Key" "Defect"

ClickAndWait Deprecated)

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.

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, the 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.