What's the actual methodology you use to do "synchronized"?

[index9]

OK, once a functional test needs to be "synchronized" what
is the actual methodology you use to do that?

[eValid]

OK, once a functional test needs to be "synchronized" what
is the actual methodology you use to do that?

Here we assume that you have a test that involves some kind of asynchronous behavior on the part of the web server that has the effect of causing a test to de-synchronize during playback. As you probably know, eValid is a fully stateful emulation of a user, and experience shows that if the playback engine "types ahead" of the server then you'll get pretty chaotic results.

De-syncs can be from a wide range of causes, but the most common is if you are using an AJAX implementation for your web application. But they also occur whenever ANY kind of server-side action takes a variable amount of time to complete outside the process of downloading the page. (eValid has built in page navigation synchronization, and it works very well; we're talking here about some kind of file download or JavaScript delivery, etc.).

The first step is to diagnose where de-syncs occur. Use the single-step command to move through your recording while studying the eventlog file to see which steps you take result in files or components being downloaded after you move to the next eValid playback command.

The other, kind of brual approach, is to set the wait time multiplier to zero -- this has the effect of asking the eValid browser to play back the script commands as fast as possible. If there is a de-sync point in your script this will surely find it.

Once you find where you need to add syncs, it's easy: Use SyncOnText or SyncOnDOMElement or any of the other built-in commands to augment your "recorded from life" script to make sure it is totally self-synchronizing...

The eValid Team