Common_Web
Note: Common keywords for all objects like button, textbox, radio button, checkbox, dropdown, list, image, table, table cell, etc.
Keyword: GETATTRIBUTEVALUE
Description: This keyword or action instructs Avo Assure Client to get the specified object/element’s attribute.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getAttributeValue | <Attribute Name> | (Optional) |
|
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.
Keyword: SETFOCUS
Description: This keyword or action instructs Avo Assure Client to set the focus on the specified element/object
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
setFocus | NA | (Optional) | NA |
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}.
Keyword: VERIFYATTRIBUTE
Description: This keyword or action instructs Avo Assure Client to verify the specified object/element’s attribute values.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyAttribute | <Attribute Name>; <Attribute_Value> (Optional) | <Attribute Exist Status>; <Value Match Status> |
|
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.
Keyword: VERIFYDISABLED
Description: This keyword or action instructs Avo Assure Client to verify whether the specified object is disabled.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyDisabled | NA | (Optional) | NA |
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}.
Keyword: VERIFYDOESNOTEXISTS
Description: This keyword or action instructs Avo Assure Client to verify if the object does not exist on the web page of AUT.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyDoesNotExists | NA | (Optional) | NA |
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}.
Keyword: VERIFYENABLED
Description: This keyword or action instructs Avo Assure Client to verify whether the specified object is enabled on the AUT Desktop page.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyEnabled | NA | (Optional) |
|
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}.
Keyword: VERIFYEXISTS
Description: This keyword or action instructs Avo Assure Client to verify the object's existence.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyExists | NA | (Optional) | NA |
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}.
Keyword: VERIFYHIDDEN
Description: This keyword or action instructs Avo Assure Client to verify if the object is hidden.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyHidden | NA | (Optional) | NA |
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}.
Keyword: VERIFYREADONLY
Description: This keyword or action instructs Avo Assure Client to verify if the object is read-only.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyReadOnly | NA | (Optional) | NA |
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}.
Keyword: VERIFYVISIBLE
Description: This keyword or action instructs Avo Assure Client to verify if the object is visible.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyVisible | NA | (Optional) | NA |
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}.
Keyword: WAITFORELEMENTVISIBLE
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.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
waitForElementVisible | NA | (Optional) | NA |
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}.
Last updated
