Besides the time limits and constraints mentioned in a recent post, are there any "bound into the code" time limits in eValid?
A fair question WalkerE.
We once considered an "insanity timeout" which would disable playback after some huge number of seconds of nothing happening, but we abandoned that idea.
It was tied into the idea, also abandoned, of disabling inputs from the desktop the the eValid browser when playback was continuing.
We thought about those two ideas and discarded them both.
Instead, we chose to leave the browser sensitive to keyboard and mouse input even when it is playing back.
So, even if playback gets stuck, you still have the COM-based desktop controls that you can use to turn eValid playback off.
This impose the small restriction that you can't interact with the eValid browser when it is actually playing back.
Well, you CAN, but it probably will mess up your test.
At one point we did have a version that had the two features above that we abandoned, and all that version did was give us trouble.
We concluded that our solution -- to keep the browser active during playback -- was the best solution.
But, neat thing happens with this design -- we now think of it as a debugging feature.
If you PAUSE the playback, the browser and all of the data collection logs are still active and you can do a lot of exploratory testing of a web application by feeding manual inputs to the browser, which thinks they are coming from playback-inspired triggers and/or events.
We have had a lot of good results using a paused eValid browser to scope out performance and behavior problems.
Hint: Try this with Detailed Timings turned on.
-- eValid Support