Explaining the eValid synchronization modes

How to apply eValid to functional testing of web applications.

Explaining the eValid synchronization modes

Postby PJHorgan » Mon Oct 11, 2021 9:10 am

Good Morning.

Tell me about the Synchronization Modes in eValid product.

Thanks
PJHorgan
 
Posts: 1
Joined: Mon Oct 11, 2021 9:06 am

Re: Explaining the eValid synchronization modes

Postby eValid » Tue Oct 12, 2021 8:58 am

PJHorgan wrote:Good Morning.

Tell me about the Synchronization Modes in eValid product.

Thanks


Sure glad to help you PJHogan.

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 .

That 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.

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.


-- eValid Support
eValid
 
Posts: 2176
Joined: Tue Jan 01, 2008 12:48 pm
Location: USA


Return to Desktop and Mobile Device Functional Testing

Design Downloaded from free phpBB templates | free website templates | Free Web Buttons