eValid is a "stateful" system

[so-urse]

You say eValid is a "stateful" system. What is that and why is it important?

[eValid]

You say eValid is a "stateful" system. What is that and why is it important?

In modern web browser enabled applications -- which is just about everything these days that involves the web -- the browser "remembers" certain facts about what is going on.

For example, when you are browsing on a banking site, the browser rememebers authentications, current transaction data (how much money you want to move from here to there), etc. Older web applications used the server to keep this data; the browser was just a viewer. The newer applications push the "work" into the browser -- away from the server -- to give the user faster response, and to minimize the server activity. A win-win type of architecture.

To TEST such a cooperative system -- browser and server interacting behind the scenes as the user interacts with the browser -- the test engine needs to know the facts that the server has asked the browser to remember. This information is called "state information" and the device that stores it then becomes "stateful".

In eValid's case, this is a come-with: eValid IS a browser and that information is naturally already there. You don't have to worry about it because eValid is a stateful engine.

eValid Test Technology Team