Why does eValid use a browser base?
Good question ChrisP.
Methods that enable a browser for testing -- and there are many ways to do this -- boil down to these two:
B. Bind a browser somehow so that you feed commands in from outside the browser.
There are a lot of these applications and they collect very valuable information.
The second method -- binding inside a wrapper of some kind so that you have direct control of the DOM -- has the advantage that you can test any page you wish, without having to respect the same-origin policy.
This approach makes for a far-superior web application testing tool.
Hope this helps!
-- eValid Support