First off, I'll start by saying that the previous perf testing efforts at my location were often thwarted by changed objects when a new build/release was deployed.
Well, I just got a new build. I'm trying to validate the scripts that I had working before, and they're all aborting with the message "Timed out validating!" (I like the exclamation - thanx Compuware!).
The odd thing is that it doesn't appear to be timing out... It scrolls through a bunch of sub requests, a bunch of checkpoints, looks like everything is going great, and then BAM it says it's timed out... There's no pause or anything? Is it maybe timing out on a previous request that was sent at the beginning of the script?
What I'm saying is that if I were to expect a timeout, I would think it would look something more like this:
Virtual User ABORTED
Timed out validating!
Nevermind. Click on Options > Workbench and select the "Script Validation" tab. There's a value that can be set for "Wait up to xx Seconds for Script Execution" - that was set to 20 seconds for some reason...
Good find. Personally, I think this is a really odd option to have in the workbench since you can just hit the Cancel button to stop validation. This option defaults to a low value as you've found and it will time out the script even though everything is working fine. This option only applies to script validation in the workbench, not a script run for an actual test in Conductor.
I don't know what a 'normal' setting would be, but I crank it up to 10 minutes (6000) because I record some long scripts and I validate them for multiple transactions and I don't want workbench validation to time out before completing.