About Javascript

[winreg]

(1) What about javascript
(2) browser extensions
(3) efficiency
(4) cross-browser testing
(5) user agent strings
(6) rendering issues

[technology]

(1) What about javascript
(2) browser extensions
(3) efficiency
(4) cross-browser testing
(5) user agent strings
(6) rendering issues

You raised a number of points and we'll address them in order.

(1) On the question of future use of JavaScript the issue relative
to simulating user behavior is that JavaScrip eats resources, and is
single-threaded to boot, and comes with a lot of constraints (the
same origin policy, for example).

Doing test playback natively in the eValid browser is very efficient
and non-interfering with anything else the browser is doing. Plus
there are some kinds of actions eValid can do that are problematic
with JavaScript, for example, DOM polling for playback
synchronization on an AJAX app.

(2) Just to be clear, eValid is not a browser extension at all.
eValid *is* a complete browser; the test recording, playback, and
analysis functions are built in CPP right alongside the browser
functionality. This is neat, and very efficient (low eValid system
overhead).

(3) "...finish a testing job very quick" is a very important
property to have. eValid is a productivity tool, so being able to
accomplish the same amount of testing in less time is seen as a good
thing to support.

(4) eValid's purpose is to test web applications, and the rendering
engine used is IE. eValid is not supposed to be used to test
whether delivered pages are compliant in other browsers. That's
cross-browser testing and there are other ways to do that. eValid
is intended to test web application functionality and performance.

(5) 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

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.html

(6) Users report being able to test their applications very
thoroughly in the MSIE context, apart from minor rendering issues.
So yes, it IS adequate to test webapps fully with eValid.