Common_Desktop
Note: Common keywords for all objects like button, textbox, radio button, checkbox, dropdown, list, tab, table, tree, etc.
Keyword: MOUSEHOVER
Description: This keyword or action instructs ICE 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: SETFOCUS
Description: This keyword or action instructs ICE 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: VERIFYENABLED
Description: This keyword or action instructs ICE to verify whether the specified object is enabled in 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: VERIFYDISABLED
Description: This keyword or action instructs ICE 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 debug, it verifies if the element is disabled and the execution status “True”/ “False” will be stored in variable {VerifyDisabled}.
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 {VerifyReadOnly}.
Keyword: VERIFYVISIBLE
Description: This keyword or action instructs ICE 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: VERIFYHIDDEN
Description: This keyword or action instructs ICE 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: VERIFYEXISTS
Description: This keyword or action instructs ICE to verify if the object exists.
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 {verifyExists}.
Last updated