Common_Web
Last updated
Last updated
Note: Common keywords for all objects like button, textbox, radio button, checkbox, dropdown, list, image, table, table cell, etc.
Description: This keyword or action instructs Avo Assure Client to get the specified object/element’s attribute.
Find the snippet of the keyword below:
In the above example, after the test case debug, the dynamic variable {MaxLengthValue} will contain the value of the specified attribute in the input field. In the above example, {MaxLengthValue} contains “2048”.
Note:
When performing getAttributeValue on a cell of a scraped table, it is mandatory to pass all 5 parameters.
getAttributeValue, when performed on a cell, will not get the attribute of the cell. Instead, it will fetch the attributes of the objects within the cell.
Description: This keyword or action instructs Avo Assure Client to set the focus on the specified element/object
Find the snippet of the keyword below:
In the above example, after the test case debug, the provided object will be focused, and the execution status “True”/ “False” will be stored in variable {setFocus}.
Description: This keyword or action instructs Avo Assure Client to verify the specified object/element’s attribute values.
Find the snippet of the keyword below:
In the above example, after the test case debug, the dynamic variable {AttributeExists} will contain ”True”/ ”False” as to whether the attribute exists. The dynamic variable {AttributeValueMatches} will contain ”True”/ ”False” as to whether the value specified in the input matches the actual value of the element’s attribute.
Description: This keyword or action instructs Avo Assure Client to verify whether the specified object is disabled.
Find the snippet of the keyword below:
In the above example, after the test case debugs, it verifies if the element is disabled, and the execution status “True”/ “False” will be stored in variable {VerifyDisabled}.
Description: This keyword or action instructs Avo Assure Client to verify if the object does not exist on the web page of AUT.
Find the snippet of the keyword below:
In the above example, after the test case debug, it verifies if the object does not exist, and the execution status “True”/ “False” will be stored in variable {VerifyDoesNotExist}.
Description: This keyword or action instructs Avo Assure Client to verify whether the specified object is enabled on the AUT Desktop page.
Find the snippet of the keyword below:
In the above example, after the test case debug, it verifies if the object is enabled, and the execution status “True”/ “False” will be stored in variable {VerifyEnabled}.
Description: This keyword or action instructs Avo Assure Client to verify the object's existence.
Find the snippet of the keyword below:
In the above example, after the test case debug, it verifies if the object exists, and the execution status “True”/ “False” will be stored in variable {VerifyExist}.
Description: This keyword or action instructs Avo Assure Client to verify if the object is hidden.
Find the snippet of the keyword below:
In the above example, after the test case debug, it verifies if the object is hidden on the web page of AUT, and the execution status “True”/ “False” will be stored in variable {verifyHidden}.
Description: This keyword or action instructs Avo Assure Client to verify if the object is read-only.
Find the snippet of the keyword below:
In the above example, after the test case debug, it verifies if the element is ReadOnly, and the execution status “True”/ “False” will be stored in variable {ReadOnly}.
Description: This keyword or action instructs Avo Assure Client to verify if the object is visible.
Find the snippet of the keyword below:
In the above example, after the test case debug, it verifies if the object is visible, and the execution status “True”/ “False” will be stored in variable {VerifyVisible}.
Description: This keyword or action instructs Avo Assure Client to wait for the element in AUT to be visible for the time specified by the timeout property in the config file.
Find the snippet of the keyword below:
In the above example, after the test case debug, it waits for the element in AUT to be visible, and the execution status “True”/ “False” will be stored in variable {WaitForElmnt}.
Keyword
Input Syntax
Output Syntax
Supported Input Formats
setFocus
NA
(Optional)
NA
Keyword
Input Syntax
Output Syntax
Supported Input Formats
verifyAttribute
<Attribute Name>; <Attribute_Value> (Optional)
<Attribute Exist Status>; <Value Match Status>
Text
Static Values
Dynamic Variables
Keyword
Input Syntax
Output Syntax
Supported Input Formats
verifyDisabled
NA
(Optional)
NA
Keyword
Input Syntax
Output Syntax
Supported Input Formats
verifyDoesNotExists
NA
(Optional)
NA
Keyword
Input Syntax
Output Syntax
Supported Input Formats
verifyEnabled
NA
(Optional)
Text
Static Values
Dynamic Variables
Keyword
Input Syntax
Output Syntax
Supported Input Formats
verifyExists
NA
(Optional)
NA
Keyword
Input Syntax
Output Syntax
Supported Input Formats
verifyHidden
NA
(Optional)
NA
Keyword
Input Syntax
Output Syntax
Supported Input Formats
verifyReadOnly
NA
(Optional)
NA
Keyword
Input Syntax
Output Syntax
Supported Input Formats
verifyVisible
NA
(Optional)
NA
Keyword
Input Syntax
Output Syntax
Supported Input Formats
waitForElementVisible
NA
(Optional)
NA
Keyword
Input Syntax
Output Syntax
Supported Input Formats
getAttributeValue
<Attribute Name>
(Optional)
Text
Static Values
Dynamic Variables
