On 08/04/2009, doki_pen <[email protected]> wrote: > sebb wrote: > > > On 08/04/2009, doki_pen <[email protected]> wrote: > > > > > > > If the start and end time are in the past, then they are ignored and > only > > > duration is respected. > > > > > > > > > > Not quite, the rule is as follows: > > > > Duration (seconds) > > IIf the scheduler checkbox is selected, one can choose a relative end > > time. JMeter will use this to calculate the End Time, and ignore the > > End Time value. > > > > Startup delay (seconds) > > If the scheduler checkbox is selected, one can choose a relative > > startup delay. JMeter will use this to calculate the Start Time, and > > ignore the Start Time value. > > > > Please see the manual where this is described: > > > > > http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Thread_Group > > > > > > > According to the manual, you are right. But in practice, I am right. The > two are not mutually exclusive, and the manual does not fully describe how > the scheduler works. Admittedly, undocumented features can change at > anytime. I use this "bug" to do what the OP was asking about. Set both > start and end to some time in the past, and set the duration to how long I'd > like the test to run. Works like a charm.
Of course. Setting the duration overrides the end time, and there's no need to provide the startup delay if the start time has already passed. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [email protected] > For additional commands, e-mail: > [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
