However, there are certain aspects to synchronization that are partially generalizable. Here is how the script development process can work as eValid browser-based tests interact with the web server in a typical AJAX application:
- Confirm Page Is Present -- Make sure that you are starting in a known place, because loss of synchronization will ruin the test.
- Find The Pivot Object -- Choose some place on the page that you know will be present and preferably unique on the page.
- Move Up/Down To Action Element -- Move structurally to the desired action point.
- Take Acton -- Apply the action (click, text input value, etc.)
- Synchronize Completion Of Response -- Make sure you KEEP synchronized.
- Repeat (Go Back to Step 1)
There are a lot more details about how this can be done -- using eValid's scripting resources -- at this page: AJAX Synchronization Loop General Description.