eValid™ -- Automated Web Quality Solution Browser-Based, Client-Side, Functional Testing & Validation, Load & Performance Tuning, Page Timing, Website Analysis, and Rich Internet Application Monitoring.

Components & Subsystems
Components and subsystems of the eValid product suite are modular and separable and can be incorporated into your product/application under an available technology license (see Note 1).

These components are delivered either as source images, executables, DLL, or in appropriate combinations. All eValid component partitioning and delivery is handled on a contracting basis and will include fully paid-up perpetual use licenses.

• Browser Architecture
  The internal assembly of eValid using standard browsing components can be instantiated into a variety of contexts -- desktop and mobile devices as well as other devices (depending on the operating system).

  Having a "test and analysis enablement" in a browser can provide a number of important advantages in terms of customer support and satisfaction, as well as the collection of crucial key performance indicators for an application. This kind of use of the technology involves exploiting the "hooks" to enablement that are built into the browser DOM.

• Recording Engine
  
  • The functional test recording engine senses certain events within the browser and issues commands (either in eValid format or in some other format) to a local file. These commands capture sufficient information to reproduce the same user action at playback time.
  • This component links directly into the browser DOM. Events in the browser trigger action within the component, which actions then generate the recorded actions.

• Playback Engine
  
  • The playback engine enables issuance of commands captured by the recording engine, and can sense the current content of the DOM, including various DOM states, to assure synchronized playback.
  • In some cases, e.g. URL navigation, the playback engine is capable of adapting to changed page content (the "adaptive playback" feature).
  • Natural navigation synchronization is augmented with proprietary event/trigger/signal combination checking.
  • At playback time the engine can monitor times (to 1 msec resolution) within the executable, and can measure the size of downloaded components using wrappers on the sub-processes that GET them from the server.
  • The playback engine records every action in the EventLog (standard format or customizable).

• DOM Access Engine
  Dynamic and independent access to the current contents of the DOM of any page that is in the browser provides a great deal of flexibility in terms of the analytics that are possible. The effective set of APIs implemented at this level parallel those of the JavaScript engine -- but because they are in parallel they do NOT interfere with operation of JavaScript. This means that normal application JavaScript operations can proceed independently of any external analytics that are imposed on the currently browsed page.

  Examples of analytic functions include:

  • IndexFindElement Command: Finds the source index of an element in the page based on a starting index number and a user-specified string match criteria.
  • IndexFindElementEX Command: Finds the source index of an element in the page based on a starting index number and a user-specified regular expression match criteria.
  • Structural commands:
  • Validate and Synchronize on Object Element Commands: These commands establish a parametric wait loop that depends on a specified DOM element property/attribute value.

• Spidering engine
  The URL and/or QueryString based recursive descent spidering engine can be constrained in terms of page properties, domains visited, or content of web pages visited. The variety of scans of clusters of URLs ("websites") is unlimited.

  Results are delivered into HTML-compatible text files so that the data that is collected can be rendered easily in custom reports. A variety of standard reports provide a ready source of examples of use of this powerful engine.

  • Recursive descent
  • Blocking URLs
  • Special URL search construction (manipulation of query strings)
  • Setup and limits Feed of pages to analytic engine (string filter model)

  ---

  Note 1: eValid patents (reverse issue date order): Patent #10,489,286 (PDF), Patent #8,683,447 (PDF), Patent #8,650,493 (PDF), Patent #8,495,585 (PDF), Patent #8,327,271, Patent #8,392,890 (PDF), Patent #7,757,175 (PDF), Patent #7,231,606 (PDF), and other patents applied for.