@Browser
Keyword: OPENBROWSER
Description: This keyword or action instructs Avo Assure Client to open a new browser.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
openBrowser | NA | (optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, the browser will be opened, and the execution status “True”/ “False” will be stored in the variable {openBrowser}.
Keyword: NAVIGATETOURL
Description: This keyword or action instructs Avo Assure Client to navigate to the given page/URL.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
navigateToURL | <URL> | (optional) |
|
Note: If any URL contains a semicolon, then it should be passed through the dynamic variable.
Find the snippet of the keyword below:
In the above example, after the test case debug, it navigates to the provided URL, and the execution status “True”/ “False” will be stored in variable {navigateURL}.
Keyword: GETPAGETITLE
Description: This keyword or action instructs Avo Assure Client to fetch the title of the current web page and save the result in the output variable.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getPageTitle | NA | {Variable}; {Status} | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, the title of the current web page will be fetched and stored in {PageTitle}, and the execution status “True”/ “False” will be stored in variable {pgtitle}.
Keyword: VERIFYPAGETITLE
Description: This keyword or action instructs Avo Assure Client to verify if the page title is the same as the title provided in the input.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyPageTitle | <Page Title> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, it verifies the title of the page is the same as the title provided in input, and the execution status “True”/ “False” will be stored in variable {verifyPageTitle}.
Keyword: GETCURRENTURL
Description: This keyword or action instructs Avo Assure Client to fetch the URL of the current web page and save the result in the output variable.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getCurrentURL | NA | {Variable}; {Status} | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, it fetches the URL of the current web page stored in {GetUrl}, and execution status “Fail”/ “Pass” will be stored in variable {currentURL}.
Keyword: VERIFYCURRENTURL
Description: This keyword or action instructs ICE to verify if the page URL is the same as the URL provided.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyCurrentURL | <URL> | (Optional) |
|
Find the snippet of the keyword below:
In the above example, after the test case debug, it verifies the URL of the page with the URL provided, and execution status “Fail”/ “Pass” will be stored in variable {verifyURL}.
Keyword: NAVIGATEBACK
Description: This keyword or action instructs Avo Assure Client to navigate to the last visited page/URL.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
navigateBack | NA | (optional) | NA |
Find the snippet of the keyword below:
For the above keyword, after the test case debug, it navigates to the last visited page/URL.
Keyword: NAVIGATEWITHAUTHENTICATE
Description: This keyword or action instructs Avo Assure Client to navigate to the specified page after valid authentication.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
navigateWithAuthenticate | <URL>;<Username>; <Encrypted Password> | (optional) |
|
Note:
This keyword can be used only if the user needs to provide credentials in the browser popup.
In order to provide encrypted password text, the User should encrypt the required text using “AES Encryption” from the utility plugin.
Find the snippet of the keyword below:
For the above keyword, after the test case debug, it navigates to the authenticated URL, and the execution status “True”/ “False” will be stored in variable {navigateAuth}.
Keyword: REFRESH
Description: This keyword or action instructs Avo Assure Client to refresh the current browser.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
refresh | NA | {variable} | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, it refreshes the current browser, and the execution status “True”/ “False” will be stored in variable {refresh}.
Keyword: VERIFYTEXTEXISTS
Description: This keyword or action instructs Avo Assure Client to verify if the input text exists in the AUT/site.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
verifyTextExists | <Input text> | {Variable};{Status} |
|
Note: Keyword returns occurrences of the text exists
Find the snippet of the keyword below:
In the above example, after the test case debug, it fetches the occurrences of the input text “Google”. It stores it in variable {Count}, and the execution status “True”/ “False” will be stored in variable {VerifyTextExists}.
Keyword: MAXIMIZEBROWSER
Description: This keyword or action instructs Avo Assure Client to maximize the current browser in use.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
maximizeBrowser | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, it maximizes the current browser, and the execution status “True”/ “False” will be stored in variable {maxBrowser}.
Keyword: CLEARCACHE
Description: This keyword or action instructs Avo Assure Client to clear the browser cookies.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
clearCache | NA | (Optional) | NA |
Note: Clears browser cookies only for IE and Chrome browsers.
Find the snippet of the keyword below:
In the above example, after the test case debug, it clears the browser cookies, and the execution status “True”/ “False” will be stored in variable {clearCache}.
Keyword: SWITCHTOWINDOW
Description: This keyword or action instructs Avo Assure Client to switch control from one window to another.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
switchToWindow | <Number> | (Optional) |
|
Note:
The numbering of windows starts from 1.
Switching between tabs is also considered a window. For example, in a scenario where the first window is opened, followed by the opening of a tab and then a new window, the input will be 3.
If the input is not provided, the control switches to the latest window.
In configuration settings, the delay attribute should be set as 0.1 or more, i.e., “delay”: “0.1”.
Max 5 windows can be switched.
Find the snippet of the keyword below:
In the above example, after the test case debug, it switches control to the specified window, and the execution status “True”/ “False” will be stored in variable {switchWindow}.
Keyword: CLOSEBROWSER
Description: This keyword or action instructs Avo Assure Client to close the current browser that is opened by the tool.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
closeBrowser | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, the application under test will be closed, and the execution status “True”/ “False” will be stored in variable {Close}.
Keyword: CLOSESUBWINDOWS
Description: This keyword or action instructs Avo Assure Client to close all the sub-windows that are open.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
closeSubWindows | <all>(optional)/<window number 1; window number 2…> (optional) | (Optional) |
|
Note:
If the input is empty, only the window that is last opened will be closed, and the focus will be shifted to the window opened prior to the closed window.
If the input is “all” (case-insensitive), all the windows the tool opens will be closed except the one on focus.
If the input is a window number (starting from 1), only the specified window will be closed. If the focused window is to be closed after the keyword is run, the focus will be shifted to the previous window. (When window number 1 is focused and closeSubWindows is performed on it, then the focus will be shifted to the second window, which now is the updated first window)
Multiple window numbers can be given as input. If multiple window numbers are specified, then these have to be 1 less than the total number of windows that are opened via the Avo Assure.
Find the snippet of the keyword below for closeSubWindows with empty input:
In the above example, after the test case debug, only the window that was last opened will be closed, and the focus will be shifted to the window opened prior to the closed window. The {closeSubWindow} variable will contain the value “True”.
Find the snippet of the keyword below, for closeSubWindows with “all” as input:
In the above example, after the test case debug, all the windows opened by the tool will be closed except the one on focus, and the {result} variable will contain the value “True”.
Find the snippet of the keyword below for closeSubWindows with “window number” as input:
In the above example, after the test case debug, only the window with window handle ‘3’ will be closed, and the {res} variable will contain the value “True”.
Find the snippet of the keyword below for closeSubWindows with “multiple window number” as input:
In the above example, after the test case debug, only the windows with window handle ‘2’ and ‘3’ will be closed, and {result} variable will contain the value “True”.
Keyword: OPENNEWTAB
Description: This keyword or action instructs Avo Assure Client to open a new window (tab) within the launched browser.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
openNewTab | NA | (optional) | NA |
Note: This keyword is not supported for IE.
Find the snippet of the keyword below:
In the above example, after the test case debug, a new window (tab) will be opened within the already launched browser, which was launched via the openBrowser keyword. The execution status “True”/ “False” will be stored in the output variable {openNewTab}.
Keyword: GETBROWSERNAME
Description: This keyword or action instructs Avo Assure Client to fetch the browser name on which the script has begun.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getBrowserName | NA | {Variable};{Status} | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, the browser name of the selected browser (for the script’s debug/execution) will be stored in the variable {BrowserName}.
Keyword: GETBROWSERTOFOREGROUND
Description: This keyword or action instructs Avo Assure Client to bring the browser (on which the AUT is being automated) to the foreground.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
getBrowserToForeground | NA | (Optional) | NA |
Find the snippet of the keyword below:
In the above example, after the test case debug, the browser (on which the AUT is being automated) will be brought to the foreground. The test step’s status will be stored in the output variable if provided.
Keyword: SENDKEYS
Description: This keyword or action instructs Avo Assure Client to send the specified keystroke(s) within the browser.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
sendKeys | <FunctionKey>; <Number(optional)> | (Optional) |
|
Note:
Multiple keys as input are not supported. For example: “ctrl+a” is not supported.
The second input specifies the number of times the specified keystrokes must be performed.
Use the setFocus keyword before this if the intention is to work on a specific object within the browser.
When keys are specified as dynamic or static variables, the content will be considered text.
This keyword can be used when the browser is minimized, or the RDP containing the browser is minimized.
Refer to the keyword sendFunctionKeys under 'Other Operations' for function key specification details.
Find the snippet of the keyword below:
In the above example, after the test case debug, a space key press is performed on the focused object within the browser.
Keyword: SAVEFILE
Description: This keyword or action instructs Avo Assure Client to save the file (via browser driver), which opens in a new tab with the file name provided in the input.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
saveFile | <FilePath>;<FileName.extn>; <Wait (in Seconds)>(Optional) | {Variable} |
|
Note:
This keyword is applicable only for web app types.
If any of the files, either .txt or .pdf, or .xml opens in a new tab. Then the user can save that file locally.
There is no need to provide the Extn in the input. ICE will save the file with extn it has downloaded.
Wait (in seconds) if provided. The ICE will wait for the specified number of seconds for the file explorer to launch.
Find the snippet of the keyword below:
In the above example, after the test case debug, the “student.html” file will be saved in the D drive, and the execution status will be stored in the output variable (if specified).
Last updated
