Common_Web
Note: Common keywords for all objects like button, textbox, radio button, checkbox, dropdown, list, image, table, table cell, etc.
Keyword: DRAG
Description: This keyword or action instructs Avo Assure Client to perform a “drag” action on the objects specified in the input.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
drag | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, it performs the “drag” action on the object, and the execution status “True”/ “False” will be stored in variable {drag}.
Keyword: DROP
Description: This keyword or action instructs Avo Assure Client to perform a “drop” action on the objects specified in the input.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
drop | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debugs, it performs the “drop” action on the object, and the execution status “True”/ “False” will be stored in variable {drop}.
Keyword: DROPFILE
Description: This keyword or action instructs Avo Assure Client to drop a file present at a specific path in the local system to an application.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
dropFile | <file path>; <file name> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, it drops the file present at the specified path, and the execution status “True”/ “False” will be stored in variable {dropFile}.
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>; <CSS> (Optional) | (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”.
If the CSS property of an element needs to be fetched, then the input specified should be as shown in the snippet below:
In the above example, after the test case debug, the dynamic variable {Padding} will contain the value of the specified CSS attribute in the input field.
For table object type:
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getAttributeValue | <Row>(optional); <Col>(optional); <objecttype>(optional); <index>(optional); <Attribute Name>; <CSS>(Optional) | (Optional) |
|
Find the snippet of the keyword when used to get the attribute of a table below:
In the above example, after the test case debug, the dynamic variable {tableAlignment} will contain the value of the specified attribute in the input field. In the above example, {tableAlignment} contains “right”.
Find the snippet of the keyword when used to get the attribute of a table cell below:
In the above example, after the test case debug, the dynamic variable {editableCell} will contain the value of the specified attribute in the input field. In the above example, {editableCell} contains “true”.
Find the snippet of the keyword when used to get the attribute of an object within a table cell below:
In the above example, after the test case debug, the dynamic variable {cellRadio} will contain the value of the specified attribute in the input field. In the above example, {cellRadio} contains “false”.
Note: For various table input variations, if the CSS property of the scraped table/ table cell/ element within the table needs to be fetched, then the last argument in all these variations should be the value “CSS,” indicating that the CSS property is required to be fetched.
Keyword: GETELEMENTTAGVALUE
Description: This keyword or action instructs Avo Assure Client to get the specified object/element’s tag value.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getElementTagValue | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, the dynamic variable {ElementTagValue} will contain the element’s tag value. In the above example, {ElementTagValue} contains “input”.
Keyword: GETTOOLTIPTEXT
Description: This keyword or action instructs Avo Assure Client to fetch the title (tooltip) present on the objects and save the result in the output variable.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getToolTipText | NA | {Variable} | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, the operation will fetch the tooltip text and store it in variable {tooltip}. The execution status “Fail”/ “Pass” will be stored in variable {tooltipStatus}.
Keyword: MOUSEHOVER
Description: This keyword or action instructs Avo Assure Client to hover the mouse on the specified object/element.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
mouseHover | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, the operation will place the mouse pointer on the object, and the execution status “True”/ “False” will be stored in variable {MouseHover}.
Keyword: RIGHTCLICK
Description: This keyword or action instructs Avo Assure Client to perform a “Right Click” action on the specified object specified in the input.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
rightClick | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debugs, a right-click operation will be performed on the element, and the execution status “True”/ “False” will be stored in variable {rightClick}.
Keyword: SENDFUNCTIONKEYS
Description: This keyword or action instructs Avo Assure Client to send the keyboard action/operation on the object specified in the input.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
sendFunctionKeys | <Function Key>; <Number> | (Optional) |
|
Note: The <Number> variable is optional and applies only to a few keys.
Find the snippet of the keyword below:
In the above example, after the test case debug, the “enter” operation will be performed on the object link, and the execution status “True”/ “False” will be stored in variable {sendKey}.
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: TAB
Description: This keyword or action instructs Avo Assure Client to perform tab operation from the object.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
tab | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debugs, the “tab” operation will be performed on the link, and the execution status “True”/ “False” will be stored in variable {tab}.
Keyword: VERIFYATTRIBUTE
Description: This keyword or action instructs Avo Assure Client to verify the value of the specified object/element’s attribute against the given input value.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyAttribute | <Attribute Name>; <Attribute_Value> (Optional); <CSS>(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.
If the CSS property of an element needs to be verified, then the input specified should be as shown in the snippet below:
In the above example, after the test case debug, the dynamic variable {PaddingLeftExists} will contain ”True” / ”False” as to whether the CSS attribute exists. The dynamic variable {Res} will contain ”True” / ”False” as to whether the value specified in the input matches the actual value of the element’s CSS attribute.
For table object type:
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyAttribute | <Row>(optional); <Col>(optional); <objecttype>(optional); <index>(optional); <Attribute Name>; <Attribute_Value> (Optional); <CSS>(Optional | <Attribute Exist Status>; <Value Match Status> |
|
Find the snippet of the keyword when used to get the attribute of a table below:
In each of the above examples, after the test case debug, the dynamic variable {tableAlignExists} will contain ”True”/ ”False” as to whether the table’s attribute exists. The dynamic variable {Res} will contain ”True”/ ”False” as to whether the value specified in the input matches the actual value of the table’s attribute.
Find the snippet of the keyword when used to get the attribute of a table cell below:
In each of the above examples, after the test case debug, the dynamic variable {tableAlignExists} will contain ”True”/ ”False” as to whether the table cell’s attribute exists. The dynamic variable {Res} will contain ”True”/ ”False” as to whether the value specified in the input matches the actual value of the table cell’s attribute.
Find the snippet of the keyword when used to get the attribute of an object within a table cell below:
In each of the above examples, after the test case debug, the dynamic variable {selRadioExists} will contain ”True”/ ”False” as to whether the table cell’s attribute exists. The dynamic variable {Res} will contain ”True”/ ”False” as to whether the value specified in the input matches the actual value of the table cell’s attribute.
Note: For various table input variations, if the CSS property of the scraped table/ table cell/ element within the table needs to be verified, then the last argument in all these variations should be the value “CSS,” indicating that the CSS property must be verified.
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 Desktop page of AUT.
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 ICE 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: VERIFYTOOLTIPTEXT
Description: This keyword or action instructs Avo Assure Client to verify the title (tooltip) present on the objects specified in the input.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyToolTipText | <Input Text> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the operation will verify the tooltip text, and the execution status “Fail”/ “Pass” will be stored in variable {verifyTool}.
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 debugs, it waits for the element in AUT to be visible, and the execution status “True” / “False” will be stored in variable {WaitForElmnt}.
Last updated
