182a wrote:Can you explain again why eValid's direct execution approach is better than using JavaScript to drive the browser?
The p
Remember in your basic physics course how the uncertainty priciple works: If you insert something into something to measure it, you may mess up your measurements. (Admittedly, with apologies to Hr. Heisenberg, that is an over simplification. But you get the idea.)
The problem with JavaScript is that it is "single-threaded" in the standard browsers so if you have JavaScript code running you don't want to interfere with it to perform test functions. A lot of non-browser-based test tools exist that use JavaScript this way, and they all have the same issue: The testing process is interfering with the process being tested.
The eValid product is a windows executable that is a direct clone of the IE browser, but achieves its effects by driving the browser -- making it a kind of "robot browser" if you will -- with internal operations on the browser API. Nothing in eValid interfers with how JavaScript works...eValid NEVER interfers with that. Instead, the actions are signalled directly into the brower.
The result is high efficiency (very low overhead) but also a very accurate emulation of IE behavior. Which is what you want from a test tool, right?
The eValid Team
by 182a » Tue Oct 12, 2010 9:56 am