Other Operations
Last updated
Last updated
Description: This keyword or action instructs Avo Assure Client to check two XML chunks present in the values of the input variables Input 1 and Input 2.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyObjects | <<Input 1>>; <<Input 2>> | NA |
|
Find the snippet of the keyword below:
In the above example after the test case debug, it checks the two XML chunks present in the values and the execution status “True”/ “False” will be stored in variable {verifyObject}.
Description: This keyword or action instructs Avo Assure Client to save the given input on the clipboard space.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
saveToClipBoard | <<Input 1>> | {Variable} |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, the given input will be saved onto the clipboard space, and the execution status “True”/ “False” will be stored in variable {saveToClipBoard}.
Description: This keyword or action instructs Avo Assure Client to fetch the data saved on the clipboard space.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getFromClipBoard | NA | {Variable} | NA |
Find the snippet of the keyword below:
In the above example, {getFromClipBoard} will contain the last saved data on the clipboard after the test case debug.
Description: This keyword or action instructs Avo Assure Client to send the function keys to the application.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
sendFunctionKeys | <function key>; <number> | (Optional) |
|
Note: ‘+’ will send two or more keys simultaneously. For example: “ctrl+a” will send all the content.
Find the snippet of the keyword below:
In the above example, after the test case debug, it sends the backspace key 6 times in the AUT.
Keyboard Value | Mapping Word | Multiple Inputs |
“Esc” | Esc | No |
“F1” | f1 | No |
“F2” | f2 | No |
“F3” | f3 | No |
“F4” | f4 | No |
“F5” | f5 | No |
“F6” | f6 | No |
“F7” | f7 | No |
“F8” | f8 | No |
“F9” | f9 | No |
“F10” | f10 | No |
“F11” | f11 | No |
“F12” | f12 | No |
“Backspace” | backspace | Yes |
“SPACE” | space | Yes |
“Insert” | insert | Yes |
“Home” | home | NA |
“Page Down” | pagedown | Yes |
“Page Up” | pageup | Yes |
“End” | end | NA |
“Enter” | enter | Yes |
“Tab” | tab | Yes |
“Shift” | shift | No |
“Ctrl” | ctrl | NA |
“Alt” | alt | NA |
“Up Arrow” | uparrow | Yes |
“Down Arrow” | downarrow | Yes |
“Left Arrow” | leftarrow | Yes |
“Right Arrow” | rightarrow | Yes |
“Windows” | windows | Yes |
“Context Menu” | menu | Yes |
“Print Screen” | printscreen | NA |
“Caps Lock” | capslock | Yes |
“Scroll Lock” | scrolllock | Yes |
“Pause” | pause | NA |
“Delete” | delete | No |
“Num Lock” | numlock | Yes |
“NUMPAD 0” | num0 | No |
“NUMPAD 1” | num1 | No |
“NUMPAD 2” | num2 | No |
“NUMPAD 3” | num3 | No |
“NUMPAD 4” | num4 | No |
“NUMPAD 5” | num5 | No |
“NUMPAD 6” | num6 | No |
“NUMPAD 7” | num7 | No |
“NUMPAD 8” | num8 | No |
“NUMPAD 9” | num9 | No |
Description: This keyword or action instructs Avo Assure Client to verify if the specified input by the user is a null value or not.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
nullCheck | <input> | {Variable}; {Status} |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, if the {TextFetched} variable contains a null, the {nullCheckStatus} will contain True.
Note:
If the input is string “null”, then the output will be True.
In the above example, {nullCheckStatus} will contain True after debug.
This keyword can be used to check against both null and None
values.
Description: This keyword or action instructs Avo Assure Client not to have any IRIS object as the anchor object for the following IRIS objects in the test script.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
disableAnchorIris | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, the reference of the set anchor IRIS object (which was set using the verifyExists keyword) will be disabled. Suppose there are IRIS objects in the proceeding test steps. In that case, these will NOT be identified based on the reference from the previously set anchor object (as the previously set anchor object was disabled).
Note: This keyword can be used when the Anchor tag is no longer required for the other IRIS objects in the proceeding test steps.
Description: This keyword or action instructs Avo Assure Client to return the status of the specified toggle key in the input field.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getKeyStatus | <Toggle key> | (Optional) |
|
Note:
The toggle key value can be num, caps, or scroll.
If no input is specified, the message ‘Please specify a valid toggle key (caps/ num/ scroll)’ will be displayed on the ICE console.
Find the snippet of the keyword below:
In the above example, after the test case debug, the status of the specified toggle button (NUM/ CAPS/ SCROLL) will be stored in the output variable (if provided).
Description: This keyword or action instructs Avo Assure client to accept an encrypted text and send the individual keystrokes of decrypted value on the specified object on focus.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
sendSecureFunctionKeys | <Encrypted Text> | (Optional) |
|
Note: To provide encrypted text as input to the sendSecureFunctionKeys keyword, the user should encrypt the required text using “AES Encryption” from the tool encryption utilities.
Find the snippet of the keyword below, with input specified directly:
In the above example, after the test case debug, the decrypted text will be entered in the specified object on focus, and the execution status “Fail”/ “Pass” will be stored in variable {output}.
