Am 03.06.2016 um 19:39 schrieb Deepak Shetty:
I dont see it in the docs - when I look at the GUI , putting a -1
automatically changes it to forever .
I'm not sure how one goes about updating the documentation -perhaps you
could file a bugzilla.
I have updated the docs in trunk after scanning the sources. "-1" is
equivalent to checking "Forever" toggle.
Normally a bugzilla entry would be a good idea to get the doc updated. A
github pull request could be use, too.
Regards,
Felix
On Thu, Jun 2, 2016 at 5:07 PM, David Luu <[email protected]> wrote:
Thanks Deepak, -1 seems to behave as "forever" though I didn't run for long
to truly confirm. Is that feature documented somewhere? If not, maybe the
JMeter docs should be updated to mention that sometime.
On Wed, Jun 1, 2016 at 9:40 PM, Deepak Shetty <[email protected]> wrote:
Hi
I cant test right now - but if I remember -1 was infinite - try it out.
If it doesnt work then you'd have to use a while controller inside your
test that could react based on passed parameters - whether it wanted to
continue or stop after awhile
regards
deeepak
On Wed, Jun 1, 2016 at 5:28 PM, David Luu <[email protected]> wrote:
I've set up and used parameterized loop count, and it's also documented
as
a best practice:
http://jmeter.apache.org/usermanual/best-practices.html#parameterising_tests
.
But I was wondering if there's a way to tell JMeter to run the loop
indefinitely, similar to what's provided in the GUI - a checkbox option
vs
providing a # in the text field. Would be nice to have the equivalent
in
command line parameterization options, perhaps something like a loop
value
of -1 or 0 means indefinite.
For now, one can use a workaround of using a really high loop count as
a
stand in to indefinite runs, but that only goes so far.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
