Sharleen wrote:Evening.
Can eValid do the testing so fast that it can FAIL because it is too quick?
Thanks
Thanks for asking Sharleen.
Yes, there ARE cases when eValid runs "too fast".
For example, if the content of the DOM has not settled down before the next command is issued you will get a problem.
One way around this is to use the "command delay" option (in the preferences) to put a constant delay in place between commands.
For example, 10 msec should be enough to prevent playback desynchronization and NOT enough to notice.
Here is the manual page.
http://www.e-valid.com/Products/Documen ... yback.html The default Command Delay is "0" but you can set it to any constant value.
If you don't want a fixed delay between commands you can insert this command in your script:
Delay 10
At point(s) where you are concerned about problems.
-- eValid Support