Custom Thread Groups - Allow to run on JMeter lower than 5.2 #691
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The latest change made in Custom Thread Groups version 3.0 allows the new JMeterThread from JMeter 5.2 to be used in ConcurrencyThreadGroup, ArrivalsThreadGroup and FreeFormArrivalsThreadGroup, but breaks compatibility with JMeter older than 5.2.
I am making a proposal to allow the use of JMeters older than 5.2 using the old JMeterThread constructor.
This applies only to ConcurrencyThreadGroup, ArrivalsThreadGroup and FreeFormArrivalsThreadGroup.
Apologies for not realizing earlier that it was possible to incorporate this possibility, I later realized that it would be easy to incorporate it and thus surely not break the execution of those who still use JMeter lower than 5.2.
I can incorporate this "version checking" and disable the new field in the UI if necessary, although it is adding code for probably a small group of users.
I look forward to hearing what you think about this proposal.