What is the biggest obstacle in testing an AJAX application?
Posted: Tue Feb 19, 2013 2:15 pmWhat is the biggest obstacle in testing an AJAX application?
With AJAX the biggest problem is "synchronization".
A "from life" test recording by eValid, which includes the delays that the human tester used while waiting for the pages under test to stabilize, will ususally work well right away.
But not if something is faster, or if you try to "get ahead" of the playback by reducing the delays.
When you do that, the playback engine will get ahead of the application, and the test will be ruined.
The solution is, when that happens, to add in synchronization steps to make sure that you don't de-sync in error.
But a much BETTER alternative is to make a self-synchronizing recording in the first place, using one of eValid's GUI-based synchronization commands to plant synchronization steps in the script. It's easy to do: You wait until the application is stable, then record a synchronization step, and THEN take the next action in the test plan. When you do this the script is almost certainly self-synchronizing.
And that in turn overcomes the biggest problem in testing AJAX applications.
eValid Test Support