Why is synchronization so important in testing an AJAX program?
I read all of these mentioned in your documentation pages, but what is the motivation?
Thanks for posting SharonA.
The basic issue with playback synchronization is this:
You want to have your tests fail when an error is detected, not when the test fails because it doesn't account for timing issues correctly.
The problem is most severe in AJAX applications.
You can always add enough Wait or Delay commands to make your test work OK, but there will ALWAYS be a time when your delays are not long enough.
A negative aspect of too-long delays is that you increase the total time of the test -- and that is not necessarily a positive.
To give you a sense of how complex "synchronization" can be, take a look at this page:http://www.e-valid.com/Products/Documen ... mmary.html
Just to be clear, the extra work you put into making a script fully self-synchronizing will pay off many times over because it'll never fail due to a fault in the test -- only with a fault in the web application being tested!
-- eValid Support