Yes, JMeter does do validation on these fields. Perhaps this should be
removed, as it is a nuisance in this case. Feel free to raise a
Bugzilla enhancment request...
In the meantime, why not use the delay and duration fields?
Or indeed use the facilities of the OS to synchronise the start of the tests.
On 25/08/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hello
I've been asked to write a load testing script which needs to be
distributed on over 10 JMeter client machines, because of the large load
created. Due to the large number of clients I've decided not to use
JMeter's remote testing capabilities. To coordinate the running of my test
I planned to use a properties file referenced when starting JMeter; my
tests are run in non-gui mode. I hoped to use property values for the
scheduler start time, end time, startup delay and duration. Unfortunately
when creating my script I'm unable to reference a property value (ie using
${__P(blahblah)} ) in the scheduler start and end time fields. The other
fields are fine, I guess the GUI must be doing some validation on the time
fields. Please tell me I'm doing something daft ;-)
Any help would be greatly appreciated.
Many thanks
Greg Peace
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
