Hello Sebb , I saw 3 reasons which Led me to implementing it this way: - looking at use case of this feature it seems to me it's different from current thread group and you might want to mix the 2 behaviours in one test plan. For me typical usage of on demand Will be to put lot of threads and very few iterations , maybe only one - code of thread group would have been too complex - currently thread group is not Much impacted and we can improve on demand Without risks on existing plans.
Regards Philippe On Saturday, July 14, 2012, sebb wrote: > I think it's good that the functionality of the onDemand thread group > now exists. > > I just wonder why it was not done as an option on the existing thread > group? > > Seems to me that would be simpler - and also easier to convert > existing test plans if required (or indeed convert back). > > Is there a reason why the functionality has to be done as a separate > class, or could the code be incorporated into the existing thread > group? > -- Cordialement. Philippe Mouawad.
