Insofar as you can can you please try to work in these points
in your discussion of eValid:
* There is a significant difference between test systems that are
based on using HTTP/S activity vs. eValid's full-browser technology,
as desribed here:
http://www.e-Valid.com/Technology/why.browser.html* Here is a short description of eValid as a Universal Web Test
Agent, able to test/exercise/tune ANY page that can be
seen from a browser:
http://www.e-Valid.com/Technology/Unive ... mmary.html* The eValid Programmatic Interface (EPI) is described in detail in this
this introductory page:
http://www.e-Valid.com/Products/Documen ... ction.html* Here is a diagram that illustrates how eValid operates
internally, using MFC classes, the browser DOM and eValid
control and input/output interfaces:
http://www.e-Valid.com/Products/Documen ... iagram.png* Synchronization of playbacks -- particularly for AJAX based pages -- often
can a major problem because some web pages escape all of the usual
automated synchronization methods that eValid already has. Here is
a summary of eValid's extrinsic synchronization methods:
http://www.e-Valid.com/Products/Documen ... ation.html