@Browser
Keyword: CLOSEBROWSER
Description: This keyword or action instructs Avo Assure Client to close the current browser that the tool opens.
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: 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: 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: 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 a 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: OPENBROWSER
Description: This keyword or action instructs Avo Assure Client to open a new browser.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
openBrowser | <Device_Number/ Simulator_Name>; <OS_Version>; <UDID > (Optional – Specify if OS is iOS) | (optional) |
|
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: 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: 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.
If there are multiple tabs in a browser window, they are numbered in their arranged order, from left to right.
Switching between tabs is also considered windows. For example, in a scenario where the first window is opened, followed by the opening of a tab and then a new window, the number of windows in this scenario will be 3.
The control switches to the latest window if an input is not provided.
The delay attribute should be set as 0.1 or more in configuration settings, i.e., “delay”: “0.1”.
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: VERIFYCURRENTURL
Description: This keyword or action instructs Avo Assure Client 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: 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: 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 that exist.
Find the snippet of the keyword below:
In the above example, after the test case debugs, it fetches the input text “Google” occurrences. It stores it in variable {Count}, and the execution status “True”/ “False” will be stored in variable {VerifyTextExists}.
Keyword: CLOSESUBWINDOWS
Description: This keyword or action instructs Avo Assure Client to close all the open sub-windows.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
closeSubWindows | (Optional) | (Optional) |
|
Note:
If the input is empty, only the current sub-window, which is on focus, will be closed.
If the input is “ALL” (case-sensitive), all the sub-windows opened by the tool will be closed except the parent.
Find the snippet of the keyword below:
In the above example, after the test case debug, it closes the sub-windows that are opened by the tool, and the execution status “True”/ “False” will be stored in variable {closeSubWindow}.
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: 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 |
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: GETDEVICES
Description: This keyword or action instructs Avo Assure Client to retrieve the serial numbers of all the connected devices/emulators.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
GetDevices | NA | {Variable}; {Status} | NA |
Find the snippet of the keyword below:
After the test case debug for the above keyword, a list of connected devices/emulators will be fetched and stored in the output variable {device}. The execution status ‘Pass’/ ’Fail’ will be stored in the second output variable (if specified).
Keyword: INVOKEDEVICE
Description: This keyword or action instructs Avo Assure Client to invoke the device/emulator specified by the serial number in the input.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
InvokeDevice | <serialNumber> | (optional) |
|
Note: Device <serialNumber> (Ex: <F7AZFG04V017>) Emulator <serialNumber> is emulator name (Ex: <emulator-5554>)
Find the snippet of the keyword below:
For the above keyword, after the test case debug, the device/emulator with the specified serial number will be invoked, and the execution status “True”/ “False” will be stored in the output variable (if specified).
Last updated
