Bug 62475 - Allow Thread scheduler to be enabled/disabled from property
Summary: Allow Thread scheduler to be enabled/disabled from property
Status: NEEDINFO
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 4.0
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-19 20:15 UTC by matthew
Modified: 2021-04-21 11:09 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matthew 2018-06-19 20:15:25 UTC
For the THREAD properties:

Number of Threads (users): ${__P(T1.threads)}
Ramp-Up Period (in seconds): ${__P(T1.rampup)}
Loop Count: ${__P(T1.loop)}
Scheduler <check box> can't set from property
Duration (seconds): ${__P(T1.durationn)}
Startup delay (seconds): ${__P(T1.delay)}
Start Time: ${__P(T1.start)}
End Time: ${__P(T1.end)}

I use external property files to control configuration. The above works great for anything that I either always want a schedule for or don't ever want a schedule for. However in many cases I want to run the same test using a schedule and in another case without one.

Currently I cannot enable a schedule with a property so I have to modify the jmx file any time I want to use or not use the schedule in a test.

It would be nice if I could define the Scheduler value through a property.

Scheduler: ${__P(T1.schedule)}

Then

T1.schedule=true

or

T1.schedule=false
Comment 1 orimarko 2021-04-21 11:09:30 UTC
Scheduler was changed, End/Start Times removed, is this issue still relevant?
Comment 2 The ASF infrastructure team 2022-09-24 20:38:13 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4804