Have you guys got a way to wait until every element on a page has 100% finally totally completely settled down?
I keep getting into trouble with tests that depend on page elements that are not present?
Thanks for asking SIhnat.
Well, perhaps ... at least some of it.
How's that for being ambivalent?
In any case, here are some of the facts about synchronization of web pages being delivered by a server to a client browser:
(1) The internal signal "document complete" may not be completely reliable, for a range of reasons too complex to discuss.
(2) The normal eValid navigation synchronization loop -- the one that is built into the eValid product -- waits for "document complete" and "download complete" and a number of other signals before concluding that the download is complete...after which the test playback can continue.
(3) But there is STILL the chance that embedded AJAX can update an element on the fly...that's the nature of AJAX.
eValid can synchronize on playback with special commands like SyncOnText, or SyncOnElementProperty, or several other commands, described here: http://www.e-valid.com/Products/Documen ... mmary.html
(4) If you build your own sync loop using one of these commands, we have found that it often helps to choose a high-index DOM element and wait till it's populated.
The higher the value of the sourceIndex the "lower" it is on the page and thus [likely] to be the last-loaded of a series of loads.
-- eValid Support