Page 1 of 1

Using Multiple Synchronizations with eValid

PostPosted: Thu Mar 21, 2019 7:00 am
by RobbieB
Morning all.

Does it make sense to have multiple synchronizations on different parts of the same page?

Or is that a little overkill with eValid?

Thanks

Re: Using Multiple Synchronizations with eValid

PostPosted: Fri Mar 22, 2019 8:44 am
by eValid
RobbieB wrote:Morning all.

Does it make sense to have multiple synchronizations on different parts of the same page?

Or is that a little overkill with eValid?

Thanks


Thanks for posting your question RobbieB.

This is, presumably, an AJAX application and the question amounts to this:

Do all of the AJAX-generated parts of a page arrive in a fixed order.

The best answer is to assume NOT!

It may be that there is an order in which page parts are loaded, but it probably is not wise to pivot one part of a test on an element that is not involved in that specific part of the test.

The commands to be concerned with are these:

http://e-valid.com/Products/Documentati ... n.dom.html

We have indeed seen cases where a cascade pf synchronizations is necessary.

But the general rule is, better safe than sorry, and what this means in practice is, synchronize first and then test for something.

Full disclosure: Even that safe procedure can fail, if the value of the element in question is varying rapidly.


-- eValid Support