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

Synopsis: The EPI feature provides a COM-based direct interface to eValid commands accessible programmatically from C/C++/C#, Java, PERL, or VB programming environments. All of the validation, synchronization, adaptive playback and activity logging features of eValid are available. The interface also provides for programmatic interface to browsed pages contents at the DOM level.

Introduction
Use of the evalid programmatic interface allows a user to convert an actual eValid script, or to construct a new eValid script, into a form that can be interfaced with:

• A C/C++/C# program execution using the eValid EPI interface.
• A JAVA desktop application execution using the eValid EPI interface. [This version available soon.]
• A PERL scripting execution using the eValid EPI interface. [This version available soon.]
• A VB scripting execution using the eValid EPI interface. [This version available soon.]

eValid playback of scripts is semi-static -- by design -- in that the scripting language is simple, generic, agnostic, and is not cluttered with unnecessary programming language details. The result is a scripting system that is an effective compromise between expressive power and clarity and ease of use.

However, in some cases the availability of the full power of a procedure oriented language offers the website tester a significant advantage For example, using eValid function calls from within a programming language would allow for the use of loops, data structures, conditional executions, extraction of values, special synnchronizations, etc. These kinds of operations can be accomplished with very low system overhead, a feature which is important to preserve the realism of the driven-browser experience and the accuracy of timing that are derived from it.

Operating Mode
Here is how this process works:

1. Record and perfect your script.evs file with eValid using the eValid record facility and possibly with manual edits to the script.
2. From the existing script create the program that corresponds to the script.
3. Play the script back and observe that the converted script is now stored in new files named "script.evs.pl" or "script.evs.cpp."
4. Each generated file is a "fragment" of code that can be dropped directly into a C/C++/C#, JAVA or PERL wrapper.
5. The eValid commands, converted into C/C++/C#, Java or PERL, are "function calls/method calls" into the EPI interface library that responds to them identically as if the commands were run in eValid.
6. The wrapper program, in C/C++/C#, Java, or PERL, is free-standing and contains ALL of the interface logic required to have eValid behave according to the instructions in the sequence of function calls/method invocations.
7. If you do nothing else to the script at this point but simply run the C/C++/C#, Java or PERL program then you will have the identically same effect as running the script in eValid.
8. You have the option, if you wish, to add logic, and data structures, and whatever other kind of programming detail you want to add in the same programming language.