ScrollIntoView
This action scrolls to view the specified object.
This action does not have any parameters.
Example:
ScrollIntoView
DownloadFile
This action clicks the link/element which will populate a download window, and then downloads the file.
The action supports and is explicitly tested for FF3, IE7, IE8. The action will not wait till the file is downloaded, this has to be handled externally by the user.
This action requires AutoIt to be installed.
- Install AutoIT from the location http://www.autoitscript.com/site/autoit/downloads/
- Click on Download AutoIt v3.
- Choose full installation.
- After the set up is completed, AutoIT installation path should be set against the Qualitia's configfile key "AutoITPath"
Input Parameters:
Parameter Name | Parameter Description | Mandatory | Data Type |
|---|---|---|---|
folderName | 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
DownloadFile "C:/ProgramData" "Qualitia"
Note:This action is tested on IE8,FF& chrome. This action is not supported on IE9,IE10,chrome<16.
On this page:
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. | 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 of this parameter can be true or false. | 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 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 | 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"
SetFocus
This action sets the focus on the specified object.
This action does not have any parameters.
Example:
SetFocus
MouseOver
This action simulates a user hovering a mouse over the specified button.
Example:
MouseOver
MouseDown
This action simulates the user pressing the left mouse button at the specified location.
Input Parameters:
Parameter Name | Parameter Description | Mandatory | Data Type |
|---|---|---|---|
X | The x-coordinate of the click. | Yes | String |
Y | The x-coordinate of the click. | Yes | String |
Example:
MouseDown "5" "10"
VerifyEnability
This action verifies the enability of the specified object.
Input Parameters:
Parameter Name | Parameter Description | Mandatory | Data Type |
|---|---|---|---|
enability | Value of this parameter can be true or false. | Yes | String |
Example:
VerifyEnability "True"
MouseUp
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. | Yes | String |
Y | The x-coordinate of the click. | Yes | String |
Example
MouseUp "5" "10"
ClickAt
This action clicks at a particular point on the object.
Input Parameters:
Parameter Name | Parameter Description | Mandatory | Data Type |
|---|---|---|---|
X | The x-coordinate of the click. | Yes | String |
Y | The x-coordinate of the click. | Yes | String |
Example
ClickAt "5" "10"
WaitForObject
This action waits for the object to exist or not exist for the maximum no of seconds specified.
If the object is found or not found before the maximum time specified, the action shall stop waiting.
If the wait time is "" then the wait time shall be the "Sync Time" time set on the Qualitia Configuration (Execution) window.
Input Parameters:
Parameter Name | Parameter Description | Mandatory | Data Type |
|---|---|---|---|
waitTime | The maximum no of seconds to wait for the object to exist or not exist | Yes | String |
existence | Boolean value to specify if the object should exist or not. | Yes | String |
Example:
WaitForObject "10" "true"
The action shall wait for maximum 10 seconds for the object to exist. If the object exists before 10 seconds elapses, the wait shall be over.
WaitForObject "15" "False"
The action shall wait for maximum 15 seconds for the object not to exist. If the object does not exist before 15 seconds elapses, the wait shall be over.
ClickAndWait
This action clicks the edit box and waits.It waits for the max sync time set in the Qualitia Configuration (Execution) window.
If the page loads before the maximum sync time, then the action will stop waiting.
Example:
ClickAndWait
In Webdriver we wait 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 will stop waiting. The condition to wait till the document is in ready state and assume that the page is loaded could however not work as expected at all times.
ClickandchooseOkOnNextConfirmation
This action clicks a button. After clicking the button, if an alert or confirmation comes up this action will accept it by clicking on Ok. If the button is clicked and no alert or confirmation comes up the action will fail.
This action does not have any parameter.
Example:
ClickandchooseOkOnNextConfirmation
StoreExistence
This action stores existence of the object under a key. The key value can be retrieved using the key name.
Input Parameters:
Parameter Name | Parameter Description | Mandatory | Data Type |
|---|---|---|---|
Key | The variable in which the existence (true/false) of the object is stored. | Yes | String |
Example:
StoreExistence "Key"
StoreChildCount
This action stores the child count of the specified object under the key name. The key value can be retrieved using the key name.
Input Parameters:
Parameter Name | Parameter Description | Mandatory | Data Type |
|---|---|---|---|
Key | The variable in which the child count will be saved. | Yes | String |
Example:
StoreChildCount "Key" This action clicks the specified object from the web application under test. This action does not have any input parameters. Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications. Example: ClickJS This action clicks the specified object from the web application under test. This action does not have any input parameters. Note: ActionClick uses underlying selenium WebDriver “Action” class to perform click action. Qualitia recommends using this action for web applications. Example: ActionClickClickJS
ActionClick
