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

Introduction
This page summarizes important differences between eValid normal operation (interactive mode, or from a Batch Mode command line), and the operation of eValid under EPI control.

Feature	Meaning And Application	eValid Native Mode	EPI Mode	Additional Comments
User Control	How the user interacts with eValid.	Normal, from the GUI or from batch commands..	Yes, you can pause and start and otherwise interact with the eValid browser WHEN PAUSED. (You can do it during playback non-paused, at your own risk)	In either mode, interacting during playback may cause undesired effects.
Event Log Output	How is the output recorded?	Usual location as Test-E.log.	Must be programmed into the CPP file to produce output. Output goes to console, must be captured to be saved. Usual > redirection works to save file.
Command Coverage	Which commands are included/covered?	100% with PROF + PAGEMAP license.	Not every command is implemented, but the most important ones are.
Custom Logs	Can you create and use custom logs (e.g. for monitoring).	Yes.	Only event log can be created.
Monitoring Output	SaveRecord command is available to create custom output.	Yes.	Yes, full C++ capabilities and access to the EventLog (if programmed).
Local Variables	Can a script keep track of values and use them in playback?	Two "abstract" variables, elementValue and sourceIndex, can be read, manipulated, and written.	Full CPP capability. Commands that involve sourceIndex return the actual value.
System Facilities	Can you get response from the underlying OS?	SsystemCall and SystemCallWait commands are available to run batch commands.	Full CPP capability.