surper wrote:Does a manually installed DOM synchronization step include
that adaptive playback feature?
By "manually installed DOM synchronization step" we assume you mean that you have a test recording that you've made from your application, to which you have added some kind of DOM synchronization.
The answer is, it depends on which command you use whether the Adaptive Playback feature is in force.
If you don't know what that is, here is an explanation: When the command finds that the page has changed and there is an ID tag available to pivot upon, the Adaptive Playback finds the "right thing to do" and does it, thereby saving your test playback from a failure.
But not every eValid command has this feature active.
If you used a command like SyncOnElementProperty, then you do NOT have Adaptive Playback (because you are synchronizing on some element that could appear ANYwhere on the page).
If you used a SyncOnSelectedObjProperty, then yes, you DO have Adaptive Playback because you have included a pivoting element number and eValid can use the ID tags in that element as the basis for finding the right OTHER element to use in case the facts don't add up for the current element.
Check the eValid documentation to be sure which commands do and do not
have the Adaptive Playback feature.
--The eValid Team