How it works

How-it-works-framework

Resource Editor

Resource Editor is a Window’s 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.

Web Application

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

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

Execution Control 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 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 the ZenVerify development team has done a masterful job of handling most of this complexity out-of-the-box.  But, HTML contyrols with custom behavior, some specialized code, and code that does not adhere to W3C standards 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. So, if you are wondering, “can ZenVerify work with our super fancy custom made whatchyamacallit?” The answer is “yes”!

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

Test Assets: including test projects, test plans, test runs, and test cases. These are saved in the central repository. This 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.

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 of your pages and widgets changed and how does this cross reference into the test assets. This cross reference enables updates made 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 one change to one test case using our Resource Editor (which is WYSIWYG) to update all 100 test cases. And, all without writing any code.

Execution Node

Selenium’s Core Technology is the foundation of ZenVerify Execution Nodes. We have built our technology to be able to leverage Selenium’s ever progressing features and functionality, now and in the future.

Virtual Users is one of our instances of the Selenium web driver running a ZenVerify managed test script. Because these Virtual Users are managed by our Execution Control Layer, we are able to correctly split your tests and run them in parallel on the available threads on one or more Execution Nodes.  Accordingly, we are able to emulate concurrent users on your site and perform load testing using our Selenium-based technology. This is an effective and affordable method to perform basic load testing.

Zen-Selenium Web Driver is a high-level Selenium API that adds intelligence to the standard Selenium script embedded in the Virtual User. For example, if you were to use our Resource Editor to create a test case that simply clicks a button on a web app, then exported that test case into Selenium it would include more than a simple command to click a button. Test automation often fails because different underlying technologies receive the “click button” command differently. ZenVerify confirms which method works best for testing your application, then uses that method. To build the same functionality natively in Selenium would be very time consuming. Accordingly, our Selenium Web Driver adds this conditional logic to the Selenium scripts so you do not have to.

Execution Nodes are any machine running a Virtual User, which can be your desktop or server or our cloud.

ZenVerify Topology

how-it-works-ZenVerify-2

3 Easy Steps to Get Started

Download & Install ZenVerify Editor & Execution Nodes on your server

Configure ZenVerify Execution Node using the credentials provided

Login to ZenVerify Web Application and start recording