> Synchronization Modes in eValid

  * Background:

    eValid has built-in synchronization features that enable the
    scripts created on standard HTML pages to produce synchronized
    playback results without any further modification.  Playback
    synchronization is automatic and invisible.

    Some tests you may wish to perform may involve session response
    times that are not purely a function of the browser rendering
    process.  This may happen, for example, when you are using some
    of the advanced eValid recording features to interact with the
    server via an Applet.

    Applications that are embedded within the HTML pages such as
    Macromedia's FLASH (*.swf) or Adobe's Portable Document Format
    (PDF) are typical examples where an additional synchronization
    step might be needed to produce the 100% synchronized playbacks.

  * Typical eValid Synchronization Commands:

    The more common synchronization step used within eValid is:

    eValid: Record Mode > Validate > & Synchronize > Text String

    which produces a SyncOnText command in the eValid script that
    references a text string which was selected during the recording
    process.

    Another synchronization step to use is:

    eValid: Record Mode > Validate > & Synchronize > Screen
    Rectangle

    which produces a xySyncRect command in the eValid script that is
    used to synchronize on an area selected by the user based on an
    internal checksum of the original image fragment.

    In general, use of this latter type of synchronization is
    necessary in sites which utilize the Absolute Recording
    (xyClick) feature of eValid.

  * Example:

    For example, consider this script passage where the
    synchronization appears before the absolution action -- to
    assure that the action has coherent meaning:

       ...
       # Synchronize on a screen rectangle before
       # proceeding with the Absolute Left Click
       #
       xySyncRect 0 497 552 15 2 0
       #
       xyLClick 0 718 556 0
       ...

    Without proper synchronization steps like the one above, scripts
    that contain commands such as xyClick's are more likely to fail
    (de-synchronize) since these commands are position dependent and
    do not use any of the standard recording protocols utilized by
    eValid.