Avo Assure
Avo Assure - User Guide v24.1
Avo Assure - User Guide v24.1
  • About Avo Assure
    • Avo Assure Lifecycle
    • Avo Assure Architecture
  • Get Started with Avo Assure
  • Explore Exciting New Features with Our Informative Video Series v24.1.0
  • Release Notes
    • Avo Assure v24.1.1
      • Session Timeout
    • Avo Assure v24.1.0 (May 2024)
      • 01. TestRail Integration
      • 02. Keyword - setBearerToken
      • 03. LDAP Configuration
      • 04. Swagger Import Definition
      • 05. Manage Project
      • 06. Unlock Test Suites
      • 07. Switch Keyword
      • 08. Testcase Assignment
      • 09. Connect With Salesforce DB Using SOQL
      • 10. Dry Run Check
      • 11.Zephyr Scale Integration
      • 12.Api Key Authorization
    • Avo Assure v24.0.3
      • 01. Bitbucket Integration
    • Avo Assure v24.0.2
    • Avo Assure v24.0.1
      • 1. Conversion of Non-Avo scripts to Avo scripts
      • 2. Custom Keyword
      • 3. Centralized Element Repository
      • 4. Tag a Test case
      • 5. Unified Reporting for Project Test Suites and Test Cases
      • 6. Journey View
      • 7. AI Testcase Generation
      • 8. Git Integration
      • 9. Avo Genius for SAP Application
      • 10. Advanced Debug
    • Avo Assure v23.2.4
    • Avo Assure v23.2.3
      • 1. rightClickTreeNode Keyword
      • 2. drag Keyword
      • 3. rightClickCell Keyword
      • 4. setTextCell Keyword
    • Avo Assure v23.2.2
      • 1. getElementColor Keyword
      • 2. drag Keyword
      • 3. drop Keyword
      • 4. rightClick Keyword
      • 5. closeSubWindow Keyword
      • 6. verifyStyle Keyword
      • 7. getDelimitedValue Keyword
      • 8. Code Snippet for CI/CD Execution
    • Avo Assure v23.2.1
      • 1. BrowserStack Integration - Mobile Web Application
      • 2. BrowserStack Integration - Mobile Native Application
    • Avo Assure v23.2.0
      • 1. Modish
      • 2. Impact Analysis
      • 3. SauceLabs Integration - Mobile Native
      • 4. Click and Add Elements - Mobile Application (iOS Native)
      • 5. BrowserStack Integration
    • Avo Assure v23.1.6
      • Module Locking Functionality
    • Avo Assure v23.1.5
      • 1. sendSecureKeys Keyword
      • 2. Enhancement Request for Testcase-Level Distribution
      • 3. Normal Execution and Scheduling Execution Enhancement - Email Alerts
      • 4. CI/CD Execution Enhancement - Email Alerts
      • 5. Mapping an Avo Test Script to an ADO Testcase
      • 6. Avo Assure Execution Status Updates in Azure DevOps
    • Avo Assure v23.1.4
      • 1. Cloud Test Providers drop-down
      • 2. Import and Export in Git format
      • 3. verifyAttachmentContent keyword
      • 4. Click and Add Elements - Mobile Application
      • 5. Advanced Upgrade Analyzer
    • Avo Assure v23.1.3
      • 1. Element Identifier Order
      • 2. Element Property Editor
      • 3. SauceLabs Integration
        • SauceLabs Integration for Web
        • SauceLabs Integration for Mobile Web
      • 4. SetOAuth2.0 keyword
      • 5. Mobile native APP, Serial Number display
      • 6. Mobile native APP, Full scrape enhancement
    • Avo Assure v23.1.2
      • 1. Object Identifier Prioritization Feature
      • 2. Azure DevOps Integration
      • 3. Import and Export Mindmap in Excel, JSON, and Complete Module(s) Format
      • 4. Element Identifier Order
      • 5. Keyword - comparePDFs
    • Avo Assure v23.1.0
      • 1. New UI/UX
      • 2. Avo Genius
      • 3. CI/CD Configuration in Avo Assure
      • 4. Mindmap Delete in Avo Assure
      • 5. Enhanced Elastic Execution Grid
      • 6. Keyword Addition to numberFormatter for Generic Object
      • 7. Keyword Stabilization Text box
      • 8. OEBS Custom keyword support
      • 9. ToolTip for all the keywords in Design Screen
      • 10. Extensive Support for Packaged App
      • 11. Combo box Keyword Stabilization
      • 12. Upgrade Analyzer
      • 13. In Sprint Automation
      • 14. OEBS SelectFromNavigator Keyword Support
      • 15. Import and Export of Module
      • 16. Delete Scenario / Screen / Testcase from DataBase
      • 17. Agent Metrics Enhancements
      • 18. Stabilization of Avo Genius for Web and Sales Force web application
      • 19. Test Execution can be exercised without having to create execution profile
      • 20. JIRA Integration Enhancement
      • 21. Import and Export of Mindmap in Avo Assure
    • Avo Assure v22.2.0
    • Avo Assure v22.1.1
  • General Information
    • Supported Technologies
  • Avo Assure Installation Requirements: Requirement Specification
    • Requirements
      • System Requirements
        • Server Side
        • Client- Side
      • Browser Requirements
    • For Windows
    • For Mobile
    • For MacOS
    • For Enterprise Resource Planning (ERP)
  • Avo Assure Platform
    • Administration
      • User Management
        • Create Users
        • Edit Users
        • Delete Users
        • User Roles
      • Agents
        • Install Agent
        • Configure Agent
      • Grids
      • Session Management
      • Project Creation
      • Authentication Configuration
        • LDAP Configuration
        • SAML Configuration
      • Feature Management
        • LLM Model
        • AI Template
      • License management
      • Manage Project
      • Locked Test Suites
    • Get Started
      • Setup–Windows
      • Setup–Mac
      • Setup-Avo Assure Client
    • Overview of Avo Assure
      • Log in Screen Overview
      • Home Page Overview
        • Edit User Profile
        • Manage integrations
          • Jira Integration
          • Azure DevOps Integration
          • Zephyr Integration
          • qTest Integration
          • ALM Integration
          • SauceLabs Integration
          • BrowserStack Integration
          • Git Integration
        • Conversion of Non-Avo scripts to Avo scripts
      • Capture Elements Screen Overview
        • Create Manually
          • Import Screen
          • Export screen
      • AvoAssure Object Identification Screen Overview
      • Design Test Steps Screen Overview
        • Export and Import of Testcase
        • Add Test Step Details
      • AI Testcase
    • Test Planning
      • Mindmap Overview
        • Creating and Modifying a Mindmap
        • Context Menu
        • Export Mindmap
        • Import Mindmap
    • Test Creation
      • Element Identification (Capturing Elements)
        • Element Identification - WEB Application
        • Element Identification - SAP Application
        • Element Identification - Oracle E-Business Suite
        • Element Identification - Salesforce Application
        • Element Identification - Desktop Application
        • Element Identification - Mobile Web Application
        • Element Identification - Mobile Application (Native)
        • Element Identification - IRIS
        • Element Identification - Web Services (API)
          • SOAP APIs
          • Import Definition SOAP API
          • REST APIs
      • Avo Genius
      • Avo Genius for SAP Application
      • Authoring Testcases
        • Testcase Authoring – WEB Application
        • Testcase Authoring– SAP Application
        • Testcase Authoring - OEBS Application
        • Testcase Authoring - Desktop Application
        • Testcase Authoring - Mobile Web Application
        • Testcase Authoring - Mobile Application (Native)
        • Testcase Authoring - IRIS
      • Element Property Editor and Prioritization
    • Test Maintenance
      • In Sprint Automation
      • Upgrade Analyzer
      • Impact Analysis
      • Element Repository
    • Test Execution
      • Create Execution Configuration
      • Executing Test Flow
        • Execute with Avo Assure Client
        • Execute with Avo Assure Agent/Grid
        • CI/CD Execution
        • Schedule
      • Execute Now - Without Execution Profile
      • Parallel Execution
      • Accessibility Testing
      • CI/CD-Harness
    • Reports Analysis
      • Test Reports Creation
        • Reports from Landing page
      • Unified Reporting for Project Test Suites and Test Cases
      • Report from Design Studio
      • Execution Report Formats
      • Reports in Avo Assure Client
      • Report Summary
      • Reports via Email
      • Agent Health Status
    • Integration
      • Test management
        • TestRail
          • Generate TestRail API Token
          • TestRail Testcase Mapping
          • TestRail Testcase Execution
        • CloudALM Overview
          • Getting started with SAP CloudALM
          • Creating a Project in SAP CloudALM
          • Creating a Test Case in SAP CloudALM
          • Setting Environment for Execution
          • Creating CloudALM project in Avo Assure
          • Mapping with CloudALM
          • Testing with CloudALM
        • Zephyr Scale
        • Jira Integration
          • Jira API Token Generation
          • Jira Configuration in Avo Assure
          • Mapping Jira Testcases in Avo Assure
          • Issue Logging
        • Zephyr Integration
          • Generate API Access Token
          • Zephyr Integration using Avo Assure
          • Mapping Test Cases(Zephyr)
          • Executing
      • Test Execution
        • SauceLabs Integration
          • Web Application
          • Mobile Web Application
          • Mobile Native Application
        • BrowserStack Integration
          • Web Application
          • Mobile Web Application
          • Mobile Native Application
      • Test Analysis
        • Azure DevOps Integration
          • Configuring and Executing(Azure Integration)
          • Issue Logging in Azure DevOps via Avo Assure reports
        • Jira Integration
      • Version Control
        • Git Integration
        • Bitbucket Integration with Avo Assure
          • Bitbucket API Token Generation
          • Creating a new Workspace in Bit Bucket
          • Create new Project Key in Bitbucket
          • Bitbucket Integration in Avo Assure
          • Bitbucket Commit/Push
          • BitBucket Restore
          • Edit/Delete Bitbucket
    • Extensions
      • Utilities
        • Encryption
        • Data Table
        • GenRocket
        • Migrate Script
          • Convert Non-Avo Script to Avo Script
          • Converted Non-Avo Script to Avo
  • Keywords
    • Generic Keywords
      • String Operations
      • Interrupt Operations
      • Date Operations
      • Database Operations
      • Mathematical Operations
      • File and Folder Operations
      • Variable Operations
      • Logical and Looping Operations
      • Skip Operations
      • XML and JSON Operations
      • Batch Operations
      • Screenshot
      • Other Operations
      • Excel Operations
    • Web Keywords
      • @Browser
      • @Browser Pop-up
      • Button
      • Checkbox
      • Radio Button
      • Textbox
      • Link
      • Element
      • Dropdown / List
      • List
      • Image
      • Table
      • Grid
      • Tablecell
      • @Object
      • @Custom
      • Common_Web
    • API Testing Keywords
      • @Web Service List
      • Web Service Elements
    • SAP Keywords
      • Operations
      • Custom Operations
      • Common Operations
      • Textbox Operations
      • Button Operations
      • RadioButton Operations
      • Checkbox Operations
      • Dropdown Operations
      • Table Operations
      • Scroll Operations
      • Shell Operations
      • Element Operations
      • Tree Control Operations
      • GridView Control Operations
      • Calendar Operations
      • Container Operations
      • Tabs
    • Desktop Keywords
      • Window
      • Button
      • Checkbox
      • Radio Button
      • Textbox
      • Element
      • Dropdown/ List
      • List
      • Tab
      • Date Time Picker
      • Email
      • Table
      • Tree
      • Custom
      • Common_Desktop
    • IRIS Keywords
      • Textbox
      • Table
      • Checkbox/ Radio Button
      • Scroll
      • Common_IRIS
    • Android Native Keywords
      • @Mobile
      • @Android_Custom
      • @Action
      • Textbox
      • Button
      • Checkbox
      • Other Components
      • Radio Button
      • Toggle Button
      • Listview
      • Spinner
      • Pickers- Date & Time
      • Seek Bar
      • Range Seek Bar
      • Number Picker
      • Common Android Native Keywords
    • iOS Keywords
      • @Mobile
      • @Custom
      • Textbox
      • Button
      • Checkbox
      • Radio Button
      • Switch
      • Picker
      • Slider
      • Date & Time Components
      • Table
      • Other Components
      • Common in iOS
    • Mobile Web Keywords
      • Link
      • @Action
      • @Browser
      • @Browser Pop-up
      • Button
      • Checkbox
      • @Custom
      • Element
      • Image
      • Textbox
      • List
      • Radio Button
      • Dropdown/ List
      • Table
      • Table Cell
      • Common_Web
    • OEBS Keywords
      • Link
      • Button
      • Checkbox
      • @Custom
      • Element
      • @Oebs
    • Mainframe Keywords
    • Custom Keyword
  • itdm
    • About iTDM
    • Release Notes
      • Avo iTDM v24.1.0
        • Avo iTDM
    • iTDM Installation Overview
      • System Requirements
        • Server Side
        • Client- Side
      • Browser Requirements
    • iTDM Platform
      • Administration
      • Get Started
        • Establish Database Connections
        • Configure Compliance Templates
      • How to use AVO iTDM to generate Test Data
        • Establish Database Connection
        • Create New Mapping
        • Create New Job
        • Configure Obfuscation and Data Generation Job
          • Data Profile
          • Manage Subset
          • Obfuscate Data
          • Manage Target (Data Provisioning)
          • Schedule
          • Preview
        • Download Test Data
      • Supported Integrations
        • Database Integrations
        • API Integrations
          • Data Discovery
            • Urls
          • Data Sub-Setting
            • JSON:Save Subset
          • Job configuration
            • Urls
            • JSON
          • Test Data Generation
            • Urls
            • JSON Save Obfuscation Inputs
            • JSON: Save Obfuscation target
          • Data Provisioning
            • Urls
            • JSON
            • JSON:Check Target Tables
          • Test Data Generation -Job Scheduling
            • Urls
            • JSON: Save Schedule Info
      • Obfuscation Techniques – as part of Obfuscate Data Module
      • Glossary
Powered by GitBook
LogoLogo
On this page
  • Keyword: CLICKELEMENT
  • Keyword: DOUBLECLICK
  • Keyword: GETELEMENTTEXT
  • Keyword: GETOBJECT
  • Keyword: GETSTATUS
  • Keyword: GETTEXT
  • Keyword: RIGHTCLICK
  • Keyword: SELECTRADIOBUTTON
  • Keyword: SELECTVALUEBYINDEX
  • Keyword: SELECTVALUEBYTEXT
  • Keyword: SETFOCUS
  • Keyword: SETTEXT
  • Keyword: SETSECURETEXT
  • Keyword: UNSELECTCHECKBOX
  • Keyword: SELECTCHECKBOX
  • Keyword: VERIFYDOESNOTEXIST
  • Keyword: VERIFYELEMENTTEXT
  • Keyword: VERIFYEXISTS
  • Keyword: DRAG
  • Keyword: DROP
  • Keyword: GETTOOLTIPTEXT
  • Keyword: VERIFYTOOLTIPTEXT
  • Keyword: MOUSEHOVER
  • Keyword: SENDFUNCTIONKEYS
  • Keyword: SENDVALUE
  • Keyword: TAB
  • Keyword: VERIFYHIDDEN
  • Keyword: VERIFYVISIBLE
  • Keyword: WAITFORELEMENTVISIBLE
  • Keyword: GETOBJECTCOUNT
  • Keyword: SENDSECUREVALUE
  • Keyword: GETALLVALUES
  • Keyword: VERIFYALLVALUES
  • Keyword: HORIZONTALSCROLL
  • Keyword: VERTICALSCROLL
  • Keyword: SENDSECUREFUNCTIONKEYS
  • Keyword: CLICK
  • Keyword: CLEARTEXT
  • Keyword: GETTEXTBOXLENGTH
  • Keyword: VERIFYTEXT
  • Keyword: GETBUTTONNAME
  • Keyword: VERIFYBUTTONNAME
  • Keyword: GETLINKTEXT
  • Keyword: VERIFYLINKTEXT
  • Keyword: VERIFYWEBIMAGES
  • Keyword: IMAGESIMILARITYPERCENTAGE
  • Keyword: UPLOADFILE
  • Keyword: DROPFILE
  • Keyword: GETCOUNT
  • Keyword: GETSELECTED
  • Keyword: GETVALUEBYINDEX
  • Keyword: VERIFYCOUNT
  • Keyword: VARIFYSELECTEDVALUE
  • Keyword: VERIFYVALUESEXISTS
  • Keyword: CMBGETALLVALUES
  • Keyword: CMBGETCOUNT
  • Keyword: CMBSELECTVALUEBYINDEX
  • Keyword: CMBSELECTVALUEBYTEXT
  1. Keywords
  2. Web Keywords

@Custom

  1. Custom Object can be used in the following scenarios:

    1. Objects which are dynamic in the web page (either position/visible text changes during execution).

    2. If object-specific keywords are not supported for the operations.

  2. Custom object does not require scraping. These keywords can be used for all valid HTML tags (Textbox, Button, Link, Image, Div, Span..), User should provide the appropriate tag name in the input: "Object Type_Input".

  3. "verifyExists" step is required before using @custom functionality. (This indicates the starting point for execution of custom keywords until it encounters the next verifyExists keyword).

Input Syntax: <Object Type_Input>; <Visible Text>; <index>; <abs (optional)>

Note:

  1. If visible text is unique then the index should be 0 (default index). (For example: link;Click Next;0) This performs the action on the link that has unique visible text "Click Next".

  2. In AUT, if there are multiple matches present for the visible text or if the visible text is not given in the input, then the user should provide index numbers appropriately.

    1. Ex 1: link;Next;2- This performs the action on the 3rd link from the reference object that has the visible text "Next".

    2. Ex 2: link;;2- This performs the action on the 3rd link from the reference object.

  3. In AUT, if there are multiple occurrences of the same text (For example: if input visible text given is 1, and there are other text fields containing 11, 21, 31, and so on.) and the need is to find the exact text specified, then the user has to provide an additional option of ‘abs’ as the last argument.

    1. Ex: link;1;0;abs

    2. Button;Submit Form;0;abs

Input Syntax Table

S.No.

Object Type

Object Type_Input

Visible Text

1

Radiobutton

radio;; <index>; <abs (optional)>

Empty

2

Checkbox

checkbox;; <index>; <abs (optional)>

Empty

3

Dropdown

dropdown; <visibleText>; <index>; <abs (optional)>

Should be the value selected in the dropdown by default/empty. Note: All single selection objects come under dropdown.

4

Listbox

listbox; <visibleText>; <index>; <abs (optional)>

Should be the value selected in the list by default/empty. Note: All single selection objects come under the list.

5.1

Table cell, Table

tablecell; <visibleText>; <index>; <abs (optional)>

Optional

5.2

Table cell, Table

table;; <index>; <abs (optional)>

Empty

6

Textbox/search, email, password, number, url, file, textarea

textbox; <visibleText>; <index>; <abs (optional)>

Optional

7

Link

link; <visibleText>; <index>; <abs (optional)>

Tool tip/name of the link

8

Image

img; <visibleText>; <index>; <abs (optional)>

Tool tip/optional

9

Button, submit, reset

button; <visibleText>; <index>; <abs (optional)>

Button name

10

Valid html tags (Eg: span, div)

<tag>; <visibleText>; <index>; <abs (optional)>

Optional

11

Grid

grid, <visibleText>, <index>; <abs (optional)>

Empty

Keyword: CLICKELEMENT

Description: This keyword or action instructs Avo Assure Client to perform a “click” action on the object as specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

clickElement

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the Click operation will be performed on the element, and the execution status “True”/ “False” will be stored in variable {click}.

Keyword: DOUBLECLICK

Description: This keyword or action instructs Avo Assure Client to perform a “doubleClick” action on the object as specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

doubleClick

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the DoubleClick operation will be performed on the button, and the execution status “True”/ “False” will be stored in variable {doubleclick}.

Keyword: GETELEMENTTEXT

Description: This keyword or action instructs Avo Assure Client to fetch the element's text and save the result in the output variable.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getElementText

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will fetch the element text and store it in variable {GetElmntTxt}, and the execution status “True”/ “False” will be stored in variable {Elestatus}.

Keyword: GETOBJECT

Description: This keyword or action instructs Avo Assure Client to fetch a specific object and use the fetched object as the reference element for subsequent custom test steps.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getObject

<Object Type_Input>; <Visible text>; <index>; <abs (optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, the operation will fetch the specified Object after the test case debug. This object can be used as a reference for all other custom keywords by specifying the last argument in the input as {{NewRefObject}}. For example, the GetStatus keyword’s input should be as follows if the new reference object must be used: <Object_type_Input>; <Visible_text>; <Index>; {{NewRefObject}}

Keyword: GETSTATUS

Description: This keyword or action instructs Avo Assure Client to fetch the object's status and save the result in the output variable.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getStatus

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will fetch the checkbox status and store it in variable {Status}.

Keyword: GETTEXT

Description: This keyword or action instructs Avo Assure Client to perform the “getText” operation on the object and save the result in the output variable.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getText

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debugs, the text of the textbox will be fetched and stored in variable {gettext}, and the execution status “True”/ “False” will be stored in variable {gtstatus}.

Keyword: RIGHTCLICK

Description: This keyword or action instructs Avo Assure Client to perform the “Right Click” action on the object specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

rightClick

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the right-click operation will be performed on the element, and the execution status “Fail”/ “Pass” will be stored in variable {rightClick}.

Keyword: SELECTRADIOBUTTON

Description: This keyword or action instructs Avo Assure Client to “select” the object specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

selectRadioButton

<Object Type_Input>; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will select the Radiobutton, and the execution status “Fail”/ “Pass” will be stored in variable {radio}.

Keyword: SELECTVALUEBYINDEX

Description: This keyword or action instructs Avo Assure Client to select the object based on the index value specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

selectValueByIndex

<Object Type_Input>; <Visible text>; <index>; <Index Value>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Note: Only numerical values are allowed in the input. The index starts with “0,” which will be the first value from the dropdown/list.

Find the snippet of the keyword below:

In the above example, after the test case debug, the provided index_value will be selected, and the execution status “True”/ “False” will be stored in variable {listbox}.

Keyword: SELECTVALUEBYTEXT

Description: This keyword or action instructs Avo Assure Client to select the value from the dropdown based on the text provided in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

selectValueByText

<Object Type_Input>; <Visible text>; <index>; <text>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debugs, the provided value will be selected, and the execution status “True”/ “False” will be stored in variable {listbox1}.

Keyword: SETFOCUS

Description: This keyword or action instructs Avo Assure Client to set the focus on the element/object specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

setFocus

<Object Type_Input>; <Visible text>; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

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 {focus}.

Keyword: SETTEXT

Description: This keyword or action instructs Avo Assure Client to set the text/string on the object specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

setText

<Object Type_Input>; <Visible text>; <index>; <value>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will set the provided text, and the execution status “Fail”/ “Pass” will be stored in variable {settext}.

Keyword: SETSECURETEXT

Description: This keyword or action instructs Avo Assure Client to accept an encrypted text and pass the decrypted value into the application.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

setSecureText

<Object Type_Input>; <Visible text>; <index>; <Encrypted Text>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the decrypted text will be printed, and the execution status “Fail”/ “Pass” will be stored in variable {secure}.

Keyword: UNSELECTCHECKBOX

Description: This keyword or action instructs Avo Assure Client to “unselect” the object specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

unSelectCheckbox

<Object Type_Input>;; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will unselect the checkbox provided, and the execution status “True”/ “False” will be stored in variable {unchecked}.

Keyword: SELECTCHECKBOX

Description: This keyword or action instructs Avo Assure Client to perform a “click” action on the object specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

selectCheckbox

<Object Type_Input>;; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will select the checkbox provided, and the execution status “True”/ “False” will be stored in variable {Checked}.

Keyword: VERIFYDOESNOTEXIST

Description: This keyword or action instructs ICE to verify if the object is not present on the web page of the AUT.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyDoesNotExist

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will verify if the object is not present on the web page of AUT, and the execution status “True”/ “False” will be stored in variable {Does}.

Keyword: VERIFYELEMENTTEXT

Description: This keyword or action instructs Avo Assure Client to verify if the element text is the same as that given in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyElementText

<Object Type_Input>; <Visible text>; <index>; <value>; <abs(optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will verify the input text, and the execution status “Fail”/ “Pass” will be stored in variable {verify}.

Keyword: VERIFYEXISTS

Description: This keyword or action instructs Avo Assure Client to verify if the object is present on the web page of AUT.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyExists

<Object Type_Input>; <Visible text>; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, it verifies if the object is present on the web page of AUT, and the execution status “True”/ “False” will be stored in variable {exists}.

Keyword: DRAG

Description: This keyword or action instructs Avo Assure Client to perform the “drag” action on the objects specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

drag

<Object Type_Input>; <Visible text>; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, it performs the “drag” action on the objects specified in input, 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 the “drop” action on the objects specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

drop

<Object Type_Input>; <Visible text>; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, it performs the “drop” action on the objects specified in input, and the execution status “True”/ “False” will be stored in variable {drop}.

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

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

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 {tool}.

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

<Object Type_Input>; <Visible text>; <index>; <value>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

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: MOUSEHOVER

Description: This keyword or action instructs Avo Assure Client to place the “Mouse pointer” on the object specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

mouseHover

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

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 specified in the input, and the execution status “True”/ “False” will be stored in variable {MouseHover}.

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

<Object Type_Input>; <Visible text>; <index>; <function key>; <number (optional)>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

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 {key}.

Keyword: SENDVALUE

Description: This keyword or action instructs Avo Assure Client to send the string values individually on the object specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

sendValue

<Object Type_Input>; <Visible text>; <index>; <value>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will set the provided text, and the execution status “Fail”/ “Pass” will be stored in variable {send}.

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

<Object Type_Input>; <Visible text>; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the “tab” operation will be performed on the link, and the execution status “True”/ “False” will be stored in variable {tab}.

Keyword: VERIFYHIDDEN

Description: This keyword or action instructs Avo Assure Client to verify if the object is hidden on the web page of AUT.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyHidden

<Object Type_Input>; <Visible text>; <index>; <abs(optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

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 {hidden}.

Keyword: VERIFYVISIBLE

Description: This keyword or action instructs Avo Assure Client to verify if the object is visible on the web page of AUT.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyVisible

<Object Type_Input>; <Visible text>; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, it verifies if the object is visible on the web page of AUT, and the execution status “True”/ “False” will be stored in variable {visible}.

Keyword: WAITFORELEMENTVISIBLE

Description: This keyword or action instructs Avo Assure Client to wait until the element is visible on the web page. Before making the step fail, this time to wait should be set in config settings using the “Timeout” property.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

waitForElementVisible

<Object Type_Input>; <Visible text>; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, wait until the element is visible on the web page, and the execution status “True”/ “False” will be stored in variable {ElementVisible}.

Keyword: GETOBJECTCOUNT

Description: This keyword or action instructs Avo Assure Client to find the number of occurrences of the object on the web page.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getObjectCount

<Object Type_Input>; <Visible text (optional)>; <index (optional)>; <abs (optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Note: <Object Type_Input>: The appropriate input object type name should be specified in the input field based on the object type.

Find the snippet of the keyword below:

In the above example, after the test case debug, it finds the number of occurrences of the object in the web page, and the result is stored in output variable {a}.

Keyword: SENDSECUREVALUE

Description: This keyword or action instructs Avo Assure Client to accept an encrypted text and pass the decrypted value into the application.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

sendSecureValue

<Object Type_Input>; <Visible text>; <index>; <Encrypted Text>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the decrypted text will be printed, and the execution status “Fail”/ “Pass” will be stored in variable {secureValue}.

Keyword: GETALLVALUES

Description: This keyword or action instructs Avo Assure Client to get all the values in the dropdown/list.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getAllValues

<Object_Type_Input>; <Visible text>; <index>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debugs, it gets all the values in the list box, and the result is stored in variable {get}.

Keyword: VERIFYALLVALUES

Description: This keyword or action instructs Avo Assure Client to verify if all of the input values provided by the user are present in the dropdown/list.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyAllValues

<Object Type_Input>; <Visible text>; <index>; <text1>; <text2>; …; <text>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debugs, it verifies if all the values are present in the list box and the execution status “Fail”/ “Pass” is stored in variable {all}.

Keyword: HORIZONTALSCROLL

Description: This keyword or action instructs Avo Assure Client to perform a horizontal scroll operation on the grid’s scrollable section given in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

horizontalScroll

<Object Type_Input>; <Visible text>; <index>; <Direction>; <No. of Scrolls>; <abs(optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, it will perform the horizontal scroll operation on the grid’s scrollable section given in the input.

Keyword: VERTICALSCROLL

Description: This keyword or action instructs Avo Assure Client to perform a vertical scroll operation on the grid’s scrollable section given in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verticalScroll

<Object Type_Input>; <Visible text>; <index>; <Direction>; <No. of Scrolls>; <abs (optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, it will perform the vertical scroll operation on the grid’s scrollable section given in the input.

Keyword: SENDSECUREFUNCTIONKEYS

Description: This keyword or action instructs Avo Assure Client to accept an encrypted text and send the individual keystrokes to the application’s element specified in the input.

Following is the syntax for performing the operation on a custom object:

Keyword

Input Syntax

Output Syntax

Supported Input Formats

sendSecureFunctionKeys

<Object Type_Input>; <Visible text>; <index>; <Direction>; <No.of Scrolls>; <abs (optional)>; <Encrypted Text>

(Optional)

  • Text

  • Static values

  • Dynamic Variables

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 custom object specified in the input, and the execution status “Fail”/ “Pass” will be stored in variable {output}.

Keyword: CLICK

Description: This keyword or action instructs Avo Assure Client to click on the object as specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

Click

<Object Type_Input>; <Visible text>;<index>;<abs(optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Note: The “Press” keyword can also be used as an alternative to “Click”.

Find the snippet of the keyword below:

In the above example, after the test case debug, the Click operation will be performed on the specified object in the input, and the execution status “True” / “False” will be stored in variable {Click}.

Keyword: CLEARTEXT

Description: This keyword or action instructs Avo Assure Client to clear the text from the textbox specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

clearText

<Object Type_Input>; <Visible text>;<index>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, it clears the text from the textbox specified in the input, and the execution status “Fail” / “Pass” will be stored in variable {Clear}.

Keyword: GETTEXTBOXLENGTH

Description: This keyword or action instructs Avo Assure Client to get the maximum text box length defined by the developer and save the result in the output variable.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getTextboxLength

<Object Type_Input>; <Visible text>;<index>;<abs(Optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Note: This keyword fetches the maximum number of supported characters by the text box, not the user input character length.

Find the snippet of the keyword below:

In the above example, after the test case debug, the maximum length of the textbox will be fetched and stored in variable {len}. The execution status “Fail” / “Pass” will be stored in variable {Status}.

Keyword: VERIFYTEXT

Description: This keyword or action instructs Avo Assure Client to verify the text in the textbox specified in the input against the value provided in the input field.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyText

<Object Type_Input>; <Visible text>;<index>;<value>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debugs, the text provided will be verified, and the execution status “Fail” / “Pass” will be stored in variable {verify}.

Keyword: GETBUTTONNAME

Description: This keyword or action instructs Avo Assure Client to fetch the button name of the button specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getButtonName

<Object Type_Input>; <Visible text>;<index>;<abs(Optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will fetch the button name and store it in variable {btn_name}. The execution status “True” / “False” will be stored in variable {BtnStatus}.

Keyword: VERIFYBUTTONNAME

Description: This keyword or action instructs Avo Assure Client to check the name present on the button specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyButtonName

<Object Type_Input>; <Visible text>;<index>;<value>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will verify the button name, and the execution status “True” / “False” will be stored in variable {VerifyButtonName}.

Keyword: GETLINKTEXT

Description: This keyword or action instructs Avo Assure Client to fetch the link's text specified in the input and save the result in the output variable.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getLinkText

<Object Type_Input>; <Visible text>;<index>;<abs(Optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will fetch the link text and store it in variable {GetLink}, and the execution status “True” / “False” will be stored in variable {LnkStatus}.

Keyword: VERIFYLINKTEXT

Description: This keyword or action instructs Avo Assure Client to verify the link text specified in the input against the value provided.

Keyword

Input Syntax

Output Syntax

verifyLinkText

<Object Type_Input>; <Visible text>;<index>;<value>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will verify the link text, and the execution status “True” / “False” will be stored in variable {VerifyLnkTxt}.

Keyword: VERIFYWEBIMAGES

Description: This keyword or action instructs Avo Assure Client to compare the image on the web page specified in the input against the image present at the path specified.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyWebImages

<Object Type_Input>; <Visible text>;<index>;<Imagepath>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Note: Supported image formats are “.png”, “.jpeg”, “.jpg”, “.gif”.

Find the snippet of the keyword below:

In the above example, after the test case debug, it compares the image on the web page specified in the input against the image present at the path, and the execution status “True” / “False” will be stored in variable {Img_verifywebImg}.

Keyword: IMAGESIMILARITYPERCENTAGE

Description: This keyword or action instructs Avo Assure Client to compare and return the similarity percentage between an image specified in the input against another image whose path is specified.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

imageSimilarityPercentage

<Object Type_Input>; <Visible text>;<index>;<Image path>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Note: Supported image formats are “.png”, “.jpeg”, “.jpg”, “.gif”.

Find the snippet of the keyword below:

In the above example, after the test case debug, the image “Android.png” will be compared with the image specified in the input. In the {result} variable, the similarity percentage of the images compared will be returned.

Keyword: UPLOADFILE

Description: This keyword or action instructs Avo Assure Client to upload a file on the object specified in the input by providing the file path from the local system.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

uploadFile

<Object Type_Input>; <Visible text>;<index>;<file path>;<file name>;<wait (in seconds)>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Note:

  • The keyword “uploadFile” works correctly only if the AUT is in the foreground.

  • If the ‘wait (in seconds)’ input is specified, then the action will be performed after the duration of the specified wait time.

Find the snippet of the keyword below:

In the above example, after the test case debug, it uploads the file present in the specified path on the specified object in the input, and the execution status “True” / “False” will be stored in variable {Img_upload}.

Keyword: DROPFILE

Description: This keyword or action instructs Avo Assure Client to drop a file on the object specified in the input by providing the file path in the local system.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

dropFile

<Object Type_Input>; <Visible text>;<index>;<file path>;<file name>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, it drops the specified input file on the specified object in the input, and the execution status “True” / “False” will be stored in variable {dropFile}.

Keyword: GETCOUNT

Description: This keyword or action instructs Avo Assure Client to fetch the total number of options present in the dropdown/list specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getCount

<Object Type_Input>; <Visible text>;<index>;<abs(Optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debugs, the tool fetches the number of values present in the dropdown/list specified in the input and stores it in {cnt}, and the execution status “True” / “False” will be stored in variable {StatusGC}.

Keyword: GETSELECTED

Description: This keyword or action instructs Avo Assure Client to fetch the selected value from the dropdown/list specified in the input and save the result in the output variable.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getSelected

<Object Type_Input>; <Visible text>;<index>;<abs(Optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Note: If the value present in the dropdown has space(s) at suffix/prefix, then the user can provide input as “1”, which will trim the spaces.

Find the snippet of the keyword below:

In the above example, after the test case debug, the selected value will be fetched and stored in the variable {sel_txt}. The execution status “True” / “False” will be stored in variable {Status}.

Keyword: GETVALUEBYINDEX

Description: This keyword or action instructs Avo Assure Client to fetch the value of the dropdown/list specified in the input by providing the index and saving the result in the output variable.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

getValueByIndex

<Object Type_Input>; <Visible text>;<index>;<index value>;<abs(Optional)>

{Variable}

  • Text

  • Static Values

  • Dynamic Variables

Note: Only numerical values are allowed in input. The index starts with “0,” which will be the first value from the list.

Find the snippet of the keyword below:

In the above example, after the test case debug, the value text will be fetched from the provided Index and stored in variable {index_val}. The execution status “True” / “False” will be stored in variable {Status}.

Keyword: VERIFYCOUNT

Description: This keyword or action instructs Avo Assure Client to verify the user-provided input count with the total number of options present in the dropdown/list specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyCount

<Object Type_Input>; <Visible text>;<index>;<count>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the count value will be verified, and the execution status “True” / “False” will be stored in variable {VerifyCount}.

Keyword: VARIFYSELECTEDVALUE

Description: This keyword or action instructs Avo Assure Client to compare the user-provided input value with the selected value in the dropdown specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifySelectedValue

<Object Type_Input>; <Visible text>;<index>;<value>;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Note:

  • This keyword requires an exact match. Due to browser rendering, the keyword will fail if the value contains trailing/leading spaces.

  • This keyword will pass only if the input value matches the value selected in the dropdown.

Find the snippet of the keyword below:

In the above example, after the test case debug, the selected value will be verified, and the execution status “True” / “False” will be stored in variable {VerifySelected}.

Keyword: VERIFYVALUESEXISTS

Description: This keyword or action instructs Avo Assure Client to verify if the input value(s) provided by the user is/are present in the dropdown/list specified in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

verifyValuesExists

<Object Type_Input>; <Visible text>;<index>;<text1>;<text2>....etc;<abs(Optional)>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Note:

  • This keyword requires an exact match. Due to browser rendering, the keyword will fail if the value contains trailing/leading spaces.

  • This keyword will pass only if the input value matches the values in the application under test.

  • If the dropdown/list contains an ‘abs’ value, this value should not be provided as the last argument. Suppose the ‘abs’ value is provided as the last argument in the input. In that case, the ICE will consider this an indication to perform the absolute comparison between the object on AUT and the specified visible text in the input.

Find the snippet of the keyword below:

In the above example, after the test case debug, the Value(s) will be verified, and the execution status “True” / “False” will be stored in variable {VerifyVal}.

Keyword: CMBGETALLVALUES

Description: This keyword or action instructs Avo Assure Client to fetch all values in the combo box and save the result in the output variable.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

cmbGetAllValues

N/A

{Variable}; {Status}

N/A

Find the snippet of the keyword below:

In the above example, Avo Assure Client will fetch all values in the combo box after the test case debug. The output will be stored in the variable {variable}, and the execution status True/False will be stored in variable {status}.

Keyword: CMBGETCOUNT

Description: This keyword or action instructs Avo Assure Client to fetch the total number of options in the combo box.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

cmbGetCount

N/A

{Variable}; {Status}

N/A

Find the snippet of the keyword below:

In the above example, Avo Assure Client will fetch the total number of options present in the combo box after the test case debug. The output will be stored in the variable {variable}, and the execution status True/False will be stored in variable {status}.

Keyword: CMBSELECTVALUEBYINDEX

Description: This keyword or action instructs Avo Assure Client to select the value from the combo box based on the index.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

cmbSelectValueByIndex

<Index_Value>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will select the value from the combo box based on the index.

Keyword: CMBSELECTVALUEBYTEXT

Description: This keyword or action instructs Avo Assure Client to select the value from the combo box based on the text provided in the input.

Keyword

Input Syntax

Output Syntax

Supported Input Formats

cmbSelectValueByText

<Input Text>

(Optional)

  • Text

  • Static Values

  • Dynamic Variables

Find the snippet of the keyword below:

In the above example, after the test case debug, the operation will select the value from the combo box based on the text provided in the input.

Previous@ObjectNextCommon_Web

Last updated 1 year ago