ljlj wrote:How does eValid achieve AJAX synchronization? I thought you could do that with simpla JScript loops? Why is eValid's method superior?
AJAX applications "de-synchronize" whenever the asynchronous operations that connect the browser with the server get out of step with the test engine playback.
Most common solutions try to put Waits in -- but we know from experience that there will always be a time when your Waits are "...not long enough..." and your test will desync.
So, eValid provides for active playback synchronization that involves checking the current contents of the page to make sure some condition obtains that guarantees that the required synchronization has happened.
This can be as simple as a "SyncOnText" command that waits for visible text, or it can be a complex synchronization done on some selected property of some element in the page.
The eValid commands that do this run direct in the browser -- they do NOT run in JavaScript. So, not only does the eValid approach assure that the AJAX behavior is left alone by the test engine, the synchronization does not interfere with AJAX at all -- nor can the AJAX interfere with the synchronization.
This is much safer and more reliable.
eValid Support
by ljlj » Fri Jun 18, 2010 3:57 pm