Can you tell me about chaining wait statements in eValid?
Does that introduce any complications along the line during my tests?
Thanks for asking KELynch.
May scripts involve first waiting for X, then after that waiting for Y and finally waiting for Z.
The script might look like this:
where the command used here is this one: http://e-valid.com/Products/Documentati ... .text.html
This is a kind of triple confirmation...you could just as well do the sync's in the reverse order and have the same effect -- provided it is a stable/static/non-changing page.
So the above really is intended to deal with a page that changes, and the required order is X > Y > Z.
However, if X changes after Y [for example] and you require X to be the same when Z is checked, they you have to probably do something like:
which will confirm all three.
The only issue now is the speed of eValid vs. the speed of the page update.
These commands are all done "in memory" whereas a change will need HTTP cooperation from the outside...so it should be safe.
-- eValid Support