Can you educate me in the hierarchy of waits in eValid?
Does one type of wait override any others?
Thanks for you question StefanI.
There are implicit and explicit wait commands.
As you know, these commands slow down playback progress until "something happens" -- with quite an available variety of what "something" would be.
The implicit wait in eValid is a built-in auto-synchronization that is based on DOM signals of various types.
In effect, any non-complete (has not arrived) signal after a page navigation will pause playback until that event happens, or until the "maximum wait time value" has been exceeded.
You can set the maximum wait time in the eValid settings menu: http://e-valid.com/Products/Documentati ... yback.html
(This group of settings also has effect in other contexts).
Explicit waits -- ones that you purposely put into your script -- can pause (or hold back) playback for a wide variety of reasons, all of which amount to holding playback until a particular user-specified state has obtained.
For example, you might wait until a certain DOM element property value equals some specified value.
In terms of hierarchy, all of the implicit waits have priority over the explicit wait commands.
There is a rule that playback can't get past a particular wait command to the next [wait] command until the wait requirement is satisfied, OR, the time limit has exceeded.
We hope that answers your question.
If you need further help, please contact us.
-- eValid Support