To be precise, eValid does not "simulate" IE. It actually is a
separate browser whose page browsing and downloading behavior uses
the same DLLs that the IE browser uses.
That's how we keep the overhead low, and never have the "hated JavaScript
interfers with everything problem" because JavaScript runs normally, etc.
* eValid has a command that can be used to set the user agent string to
any value. This command makes it possible to cause eValid to report to
a server that it is ANY kind of browser, a feature that is useful for
validation of web applications beyond the IE context that eValid supports:
http://www.e-Valid.com/Products/Documen ... tUserAgent* eValid has a related special capability to mainpulate HTTP/S headers so
that a tester can set up unusual header combinations, including trying
special "user agent strings", as described here:
http://www.e-Valid.com/Products/Documen ... aders.html* Here is an illustration of how effective eValid's SetUserAgent string
can be in testing applications that involve multiple browser types:
http://www.e-Valid.com/Products/Documen ... ation.htmlBut, what is the measurement issue you're dealing with? You might also like:
* Here is a technique that uses some special properites of eValid to
observe what is happening in a complex, asynchronous web page or
web application:
http://www.e-Valid.com/Products/Documen ... iming.html