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

Summary
The eValid Programmatic Interface (EPI) is a COM-based DLL that implements a variety of functions to support eValid operation via a programmatic interface that is based on control of eValid via the eValid Script Language with additional methods/functions for special purposes. See the Overview of EPI Organization.

Features & Facilities Provided
Here is a summary of the facilities provided with the eValid EPI feature:

• COM-type DLL that interfaces to popular programming environments.
• Out of the box operation with C++ on Windows.
• Direct access to most eValid script commands to save programming work and encapsulate existing internal synchronization modes.
• Immediate access to eValid playback responses (response times and result status) via a special in-memory internal communication block/region.
• Direct access to the DOM of the page that is currently in the eValid browser, to allow reading and setting of any page attribute.
• Full access to result codes, so that a driver program can take advantage of the consequence of commanded actions.
• All eValid playback synchronization and control features remain available to the eValid instance running under EPI control.

Specification Details
These are the technical details on use and operation of the EPI feature.

• The epi.dll COM library includes the interface to and from the current active eValid browser.
• For C++ (CPP) operation the corresponding CPP epi.h header file is supplied with the product.
• EPI operation support structures and files with PERL, VB, and JAVA will be released as soon as available. The epi.dll will operate with any Windows environment.
• eValid script commands implemented in the interface include most of the commands necessary to navigate, validate, analyze and synchronize browser actions, in these categories:
  • Navigation: 7 commands.
  • Timing and Stopwatch: 6 commands.
  • Cache Management: 2 commands.
  • Wait Time/Date Manipulation: 10 commands.
  • Synchronization Support: 7 commands.
  • Playback Oriented: 11 commands.
  • Element Oriented: 12 commands.
  • Link Check Wizard: 2 commands.
  • Validation: 20 commands.
  • String Matching: 2 commands.
  • DOM-based Synchronization Support: 4 commands.
  • Extracting DOM, Page and Screen Content: 10 commands.
  • Index Motion: 7 commands.
  • Absolute Position: 9 commands.
  • Window Management: 3 commands.
  • Keyboard & Desktop Operations: 1 command.
  • Script Manipulation and Annotation: 3 commands.
• eValid features such as Automatic Synchronization and Adaptive Playback are active inside the eValid browser even when controlled through the EPI.
• The EPI interface requires at least a current EPI and PROF feature key. Some commands may also require a GEN or PAGEMAP feature key for correct operation. Web access in revenue licenses is not required.
• The EPI interface is also activated with EVAUTO/EVAL licenses which require web access.
• Communication from the controlling program and the eValid instance that is launched is direct "in-memory" for very low system overhead time. In-the-browser timings are accurate to << 1%.
• Control of the contents of the DOM of the current page with get_NumElements, get_ElementAttribute and put_ElementAttribute commands/methods.
• Direct access to the complete standard eValid playback-time event logfile.
• Special built-in commands/methods to extract specific values from current eValid playback-time event logfile.