Do you have any recommended maximum length of a test?
Another way to ask this might be, beyond how many test steps is the state of the browser no longer going to be repeatable.
There's no imposed limit on the length of time an eValid script can play back, and we have seen some scripts that take 15+ minutes the execute.
One script we worked with recently had about 250 separate steps (about 500 commands overall) and took about 10 minutes to play. That's quite long!
That is quite long, and the elapsed playback time, even when accellerated by reducing waits to the minimum through synchronization, imposes delay when you are trying to modify or debug a script.
Obviously there is no general rule, but we would argue that a playback time above 5 minutes (300 seconds) is going to run into either state-loss or tester-patience-loss issues before long.
____________________
eValid Tech Support
No comments:
Post a Comment