techr9 wrote:Isn't your API just a command-oriented framework for a web browser as a test driver?
Yes, that is a good and fair characterization of the eValid system.
In fact, eValid began from the simple notion that the best way to drive a web browser enabled application is to use a browser as the test bed.
So, indeed, eValid's command language is a very good framework for driving a web application. However, there are several important differences:
(1) eValid includes a recording engine that creates scripts that play back 99.99% of the time without modification. That saves YOU a lot of work.
(2) There are built-in timing and record-keeping logs -- the main one is the eValid EventLog -- that take care of recording key performance data.
(3) There is an all-important set of commands that support "structural testing" of web applications -- so that after making a recording you can modify a script so that it will run independent of a wide range of structural and content changes in the web page.
Overall, we believe that eValid is the most powerful form of web application test engine around...eValid has never seen a web application that can't be tested thoroughly with eValid's capabilities.
The eValid Team
by eValid » Tue Nov 30, 2010 8:14 am