Avo Assure - v 22.2.0
Comment on page

Working with Avo Assure

Object Identification

Object identification is the process of uniquely identifying objects present in the application under test (AUT). There are two main ways an object is identified:
  1. 1.
    Object property-based identification.
  2. 2.
    Image-based identification.
In object property-based identification, objects are identified by one or more unique properties that the object has. For example object type, object name, etc.
In image-based object identification, the objects of the AUT are uniquely characterized as images, and image recognition is used to detect the objects to perform the required action.
These processes become more complicated when the objects are dynamically changing, do not have any unique properties or there are no easy ways of identifying the properties of the objects (e.g. non-web based applications).
Avo Assure uses a Robust Object Recognition Algorithm (RORA) and IRIS (Image Recognition in Scraping) to identify all such objects with a single click. Objects can be identified and differentiated by the algorithm’s careful understanding of the minute differences in properties between objects.
For more information, refer here.
Avo Assure also allows the user to prototype objects which can be mapped to actual objects in the future. This feature allows the user to author test cases even when the AUT is under development.
For more information, refer here.

Test Case Authoring

Test case authoring is a combination of actions being performed on objects identified in the AUT and validating that the responses of these actions are as intended.
Traditionally, test case automation requires that the actions that need to be performed be scripted or programmed. This is in addition to the framework that needs to be designed.
Avo Assure is a platform that addresses these key issues by providing an inbuilt framework and scriptless test case authoring, reducing the total cost of ownership. This approach empowers all users to define and execute their tests without the need to write any kind of code, freeing them from the automation specialist bottleneck.
For more information, refer here.
In addition to scriptless test case authoring, Avo Assure enables the user to verify the test case authored, in different environments (browsers, emulators, devices), add dependent test cases already present, and also change the object properties if required.

Test Execution

Test execution is defined as the activity that runs a test on a component or system producing actual results.
Test execution involves executing the test scripts in the test environment on the AUT. In test automation, this can be achieved in one of the ways:
  1. 1.
    Running the test that has been scripted on a local machine.
  2. 2.
    Running the test scripts in parallel on multiple machines or the cloud.
The Test Cases can be scheduled to execute at a particular time or can be triggered from an external orchestrator tool. This is particularly the case in the continuous testing process.
Avo Assure provides the following methods of test execution.
  1. 1.
    Sequential Execution
  2. 2.
    Parallel Execution
  3. 3.
    Smart Execution
  4. 4.
    Smart Scheduling
In addition to the above, Avo Assure also integrates seamlessly with orchestrator tools through its set of open APIs.
For more information, refer here.


Reporting is defined as collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform stakeholders.
Reports make the user aware of the status of the success or failure of the tests that have been executed and also help in finding out potential defects.
Avo Assure provides an inbuilt reporting mechanism that provides detailed reports both at the summary level and step level with screenshots captured for every step.
The reports are provided in multiple formats (HTML, PDF, JSON). In addition, Avo Assure's Reports plugin integrates with defect tracking tools to log defects automatically in the tools and embeds the defect number in the report against the failed steps.
For more information, refer here.


The software testing life cycle includes the following phases.
  1. 1.
    Requirements Phase
  2. 2.
    Planning Phase
  3. 3.
    Analysis Phase
  4. 4.
    Design Phase
  5. 5.
    Implementation Phase
  6. 6.
    Execution Phase
  7. 7.
    Reporting and Closure Phase
Although test automation very often is part of the implementation phase and the execution phase only, the artefacts of the other phases too have to be integrated with the test automation tool.
Avo Assure integrates with the tools in the ecosystem whether it's a third-party device lab, CICD tools, source code repository, or bug reporting tool. Avo Assure provides inbuilt integration with the industry’s leading ALM tools and provides APIs adhering to open API standards that can be used to integrate with any tool.
For more information, refer here.

Page Object Model


Page object model (POM) is a popular design pattern used in test automation.
In the page object model, each page of the application under test (AUT) is represented as a class, and the objects (elements) within this page are defined as variables of this class.
All the actions on these objects can then be implemented as methods using which testers can perform operations on the application under test.
  1. 1.
    Maximum Reusability
  2. 2.
    Ease of Maintenance
  1. 1.
    The initial investment in effort and time to structure the framework.
  2. 2.
    Tedious identification of pages of the application under test and mapping it to test cases.

Avo Assure and POM

Avo Assure utilizes the POM concept, hence each test flow that needs to be automated is divided into nodes which are called Screens. These Screens correspond to each page of the AUT.
All the elements belonging to a particular page of the AUT are identified and mapped to a Screen. All the actions that can be performed on these objects (identified in this Screen) are then implemented in the child nodes of the screen which are called Test Cases.
Avo Assure eases the challenges of the traditional POM concept by facilitating the user to design the POM-based structure of the test flow using its Mindmaps plugin.
For more information, refer here.