I often see on stackoverflow and during my training / consulting work a misunderstanding about duration of test when user: - configures scheduler with a duration - but keeps Loop Count to a limited number The question is then, how come my test didn't last for the expected duration ? To disambiguate this, I propose to add this note in UI: If Loop Count is not -1 or Forever, duration will be min(Duration, Loop Count * iteration duration)
Author: pmouawad Date: Thu Nov 15 22:14:15 2018 New Revision: 1846687 URL: http://svn.apache.org/viewvc?rev=1846687&view=rev Log: Bug 62914 - Add a hint in Thread Group UI about duration of test Bugzilla Id: 62914 Modified: jmeter/trunk/src/core/org/apache/jmeter/resources/messages.properties jmeter/trunk/src/core/org/apache/jmeter/resources/messages_fr.properties jmeter/trunk/src/core/org/apache/jmeter/threads/gui/ThreadGroupGui.java jmeter/trunk/xdocs/changes.xml
@philippe, I find that the warning distracts me. What do you think if the remove the warning and rename "duration" label to "maximum test duration" instead? That should mean the threads won't last more than "maximum test duration".
(In reply to Vladimir Sitnikov from comment #2) > @philippe, I find that the warning distracts me. > > What do you think if the remove the warning and rename "duration" label to > "maximum test duration" instead? > > > That should mean the threads won't last more than "maximum test duration". Although not very sexy, I think this warning is useful, I saw many questions on SO where this was not understood. Yes the label change is a good idea but is not enough IMO
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4921