How does eValid handle page refreshes...any thoughts about that?
I'm testing a complex AJAX application and I'm getting errors with synchronization.
Welcome aboard DianeT!
When you have AJAX applications running please remember:
The eValid product has Reload command: (Reload wid) where wid is the window id sequence number.
If you leave this parameter out, eValid assumes wid = 0.
This refreshes the window the same way the refresh button refreshes any browser.
If the underlying DOM has been manipulated and/or changed by the AJAX activity then you will see the "most recent" changes in the rendered screen.
In some cases it is wise to issue a Reload wid command before searching the DOM for a specific page element, but this is not perfect.
Instead, you may want to rely on am explicit synchronization command, as explained here: http://e-valid.com/Products/Documentati ... guide.html
This will make sure that your test actions start at a known place, but if the AJAX updating is happening after you achieve that specific synchronization the you may STILL have aberrant behavior.
The bottom line is, until you have run your test script many times and convinced yourself that it is reliable, you have no guarantee.
Even then, we have seen cases where ultra-reliable test scripts that literally bristle with synchronization steps fail from time to time.
Such are the vagaries of web application testing.
-- eValid Support