Why eValid is able to handle AJAX?
Posted: Tue Aug 18, 2009 4:06 pmCan you explain more why eValid is able to handle AJAX and the other solutions can't?
augsum wrote:Can you explain more why eValid is able to handle AJAX and the other solutions can't?
That's a fairly general question, but in a nutshell the main attribute eValid has that allows it to handle AJAX is that it is a self-contained browser and does not rely on plugins or JavaScript interpretation or any other "trick" that might be used. eValid's a full browser but with test functions built inside.
An AJAX application needs to have a free hand with the JavaScript engine -- that is what makes it "go" -- and eValid's architecture neatly avoids interfering with the JavaScript in any way.
That said, then, the NEXT main advantage eValid has is that if you DO need to synchronize playback with some internal event, then eValid can do that without having to interfere with the JavaScript that is keeping your AJAX engine going.
There are special "DOM Synchronization Commands" which make sure that a test playback meets a specified criteria before going to the next command -- in effect, that forces the synchronization to be accurate even when the brower-plus-JavaScript engine is running asynchronously.
The eValid Team