vxvalley wrote:You say eValid "preserves the client-user state". What does that mean in practical terms and why is that important?
By "client-user state" we mean that the entire state of the web application, as seen by the client browser, is fully preserved by eValid.
This happens because the eValid engine is a fully featured, self-contained browser, with all the bells and whistles that go with that.
Accordingly, certain kinds of state transitions are "remembered" by eValid -- just as they are rememberd by your regular browser. This includes cookie and cache information but, perhaps more importantly, this includes internal-state details that are maintained in the browser's local memory. This kind of information is kept in the DOM or in internal variables that the using application may employ to record login details and other session-dependent material.
In a slightly different, the stateful nature of eValid makes it possible to automatically perform tests on AJAX applications that can't be done without having such memory. That is, HTTP/S is a "stateless" protocol, but when combined with a browser that uses HTTP/S to communicate to a server, you have state preservation options available.
At the end of the day, using a full browser achieves 100% realism and 100% reproducibility. Both of these features contribute the eValid's power and utility.
eValid Technology Group
by vxvalley » Fri Jan 07, 2011 4:15 pm