Chadd wrote:Why do you have to have a special "wait/sync/act" protocol for recording AJAX? Why can't you do it automatically?
The problem is, every AJAX implementation is "different" from every other one, and the variations in how individual teams build AJAX support into their web applications makes it impossible to apply a general rule.
The one thing in common with AJAX is that there is asynchronous page loading work going on in the background.
So this presents a technically difficult challenge: How to synchronize playback into a fundamentally asynchronous process, that is AJAX. Remember the "A" in AJAX stands for asynchronous!
The wait/sync/act simplified protocol is just a way to make sure your recording of an AJAX application always includes a check -- before taking an action -- to make sure that the action you take really IS present (so the action will be meaningful). The simplest command to do this is to use the SyncOnText (Ctrl-Y) command after you highlight something on the page that show that it's there. [Of course, you can't highlight it unitl it's there and that, after all, is the point!]
There are other synchronizations available, but this method is the easiest to remember and use.
eValid Support Team
by Chadd » Mon Jul 16, 2012 4:19 pm