"Run for duration" in controller behaves like "Run until completion" when the the given number of iterations is done executing?
-
True
-
False
In LoadRunner controller, when you set 'Run for duration' with a specific number of iterations, once those iterations complete, the behavior is effectively the same as 'Run until completion' - the vusers stop after finishing the specified iterations. The statement is True.
The statement is TRUE, so 'False' is marked wrong. In a JMeter Thread Group, the scheduler Duration is only an upper bound (a cap), while a finite Loop Count sets the number of iterations. The thread group ends at whichever limit is hit first. If the specified number of iterations finishes before the Duration expires, each thread has no more work and exits — JMeter does NOT keep idle threads alive to fill the remaining duration, nor does it start extra iterations beyond the loop count. Hence, when the iterations are done, 'Run for duration' effectively behaves like 'Run until completion' and the test stops early. Duration only takes precedence in the opposite case (cutting the test short if the loop hasn't finished). The correct answer is 'True' (id 531600).