Functional & UI Testing – Heuristic Based Test Automation Tool

# Customer Details:

The client is a US-based custom product development & outsourcing firm. They came up with an innovative & creative idea about an automation tool.

Tool has been built from the ground up to simplify the complex tasks of automation. It manages the complexity and exposes a simple and intuitive GUI to its users. Behind it’s simple GUI, ZenVerify hides an extremely powerful engine. This heuristic based, extensible engine enables automation of the most complex workflows.

ZenVerify has been designed for global teams to share information. It enables multiple parties to review information and collaborate in real-time.

Business Challenges:

Many competitors in the market

Effective Communication and Collaboration

Demanding Skilled Resources

Selecting a Proper Testing Approach

High Upfront Investment Cost

Application/ Product Details:

Resource Editor is a Windows desktop record-and-edit application with an embedded internet browser. The Resource Editor automatically records your actions as you surf your target application within the embedded web browser. It also allows you to graphically edit your recorded test cases.

Usability Layer: This exposes the test management and administration functionality using web browsers.

Reporting Layer: The Resource Layer tracks the test results, including the time required to execute each test and presents the results in real-time.

Execution Control Layer: This layer manages the schedules of the Virtual Users and the parallelization of test runs according to the available threads on each available Execution Node. This is the primary layer responsible for Load Testing and Performance Monitoring.

Extension Layer: It translates ZenVerify’s capabilities to domain-specific coding standards. Dynamic page content, AJAX and JavaScript actions can be very challenging for any automated platform to test. We are proud that our development team has done a wonderful job in handling most of this complexity out-of-the-box but, HTML controls with custom behaviour, some specialized code and code that does not adhere to W3C standards. It sometimes requires us to insert an extension into the Fingerprinting Framework for a specific client. These extensions essentially translate how your custom code maps to the code our platform already understands. ZenVerify works with our super fancy custom controls.

Fingerprinting and Central Repository Layer: It is the heart of the platform and includes:

a) Test Assets: These include test projects, test plans, test runs, and test cases. These are saved in the central repository and maintains one or more projects. Each project can have any number of versions. Each project version contains the pages, page widgets and test cases within the target application.

b) Page And Widget Fingerprints: Every test created in ZenVerify results in page and widget fingerprints of your web application being saved in ZenVerify’s Central Repository. When your application changes, ZenVerify detects which all pages and widgets are changed and how does this cross-reference influence the test assets. This cross-reference enables updates turned to a single test case to be propagated to all other impacted test cases. Accordingly, if you have 100 test cases impacted by changes to a single page, then you only have to make a single change to one test case using our Resource Editor (which is WYSIWYG) and update all the other 100 test cases, without writing any code.


Analysing the feasibility of the existing requirements.

Assessment of the other automation tools in the marketplace.

Reframing the requirements after discussion with the client.

Planning & Training.

Automation of Scripts, Creating Sanity and Utility Scripts.

Testing, Execution and Integration with ZenVerify.

The AppSierra team members are primarily Automation Experts in various automation tools available in the marketplace. Our team was responsible for exploring and analysing the different automation tools and creating an assessment report of all those tools which include their features and drawbacks. Designing Automation Strategy and Planning, training the Core Black-Box testing team to ramp them up on technical skills required for ZenVerify and handling Client interactions.


We had daily calls with the client to understand his expectations from the application.

We reframed the requirements based on the feasibility.

There were regular weekly and daily meetings to track progress and review tasks.

JIRA was used for tracking the issue and maintaining the sprint wise deliveries.

Test scripts were created in JIRA by using a Zephyr plugin as per the discussions and the manual provided by the client.

Regression testing of the application using the test scripts.

After the final QA sign off, acceptance testing was done which also involved the customers.