Understanding how eValid runs from the DOM better

[DonaldB]

Hi.

You always say eValid runs "from the DOM" but I'm not sure what that means, exactly.

Can you explain it more clearly?

Thanks

[eValid]

Hi.

You always say eValid runs "from the DOM" but I'm not sure what that means, exactly.

Can you explain it more clearly?

Thanks

Thanks for asking, DonaldB.

eValid obtains most of effects by manipulating the Document Object Model (DOM) that is maintained inside the browser.

The DOM is an internal structure that the user ordinarily does not see.

It works in a kind of "private loop" to create and maintain what you see on the browser face.

Entries in the DOM are called "DOM Elements" and they are numbered 0, 1, 2... in a thread that is updated with each change in the state of the browser.

Changes, or "triggers," can be initiated by the user or by some external event.

eValid provides a way of looking into the tree using the PageMap feature, described in part with this page: http://e-valid.com/Products/Documentati ... cture.html

eValid was the pioneer in this approach, fielding a product as early as late 1999, based on internal prototypes developed from 1998 onwards.

Manipulating the DOM for purposes of testing a web application was very effective, and eValid's lead was followed -- over the years -- by WATIR, Selenium, and finally WebDriver, which is now standard in all of the major commercial browser systems.


-- eValid Support