Here are some followup pages...
The point about JavaScript is this: eValid uses direct
execution in playback and does NOT use a JavaScript-based
playback method (as other products do). This means that
when you have an AJAX application you can know that eValid
is NOT interfering with the operation of the AJAX parts
(which are implemented in JavaScript).
* Here is an inventory of movie-like illustrations of a range of
eValid operational modes:
http://www.e-Valid.com/Products/Documen ... ntory.html* We find from experience that many playback problems arise because
the eValid system "remembers" initial state, and you have to take
this fact into account when creating scripts. Here's a summary
description of how this kind of problem can be recognized and resolved:
http://www.e-Valid.com/Products/Documen ... tions.html* eValid rememebers the internal state of a test, and sometimes
controlling the internal state is critically important. Here
are some recommendations about how eValid supports maintaining
internal state:
http://www.e-Valid.com/Products/Documen ... state.html* We have very high confidence in eValid's ability to play back
tests of ANY website, and we even have a 100% guarantee of this:
http://www.e-Valid.com/Promotion/guarantee.html