Hi, I too find it not worth investing in. For some of the problems mentioned in the description, there are easy workarounds like using a parameter in sleep controllers or copying the test plan into a "debug mode thread group" which runs only one thread with one iteration...
Anyhow, I do think I will use such feature, if it will get implemented. Shmuel. בתאריך 2012 6 3 02:01, מאת "sebb" <[email protected]>: > On 2 June 2012 20:23, Philippe Mouawad <[email protected]> wrote: > > Hello, > > Regarding issue: > > > > - https://issues.apache.org/bugzilla/show_bug.cgi?id=53330 > > > > I think of the following implementation: > > I'm not sure it's worth implementing. > > > - Create a DryRunTreeCloner that extends TreeCloner > > - This one will call a new method "handleDryRun" on each TestElement > > - boolean handleDryRun(); returns true if TestElement should be added > to > > Test tree > > > > Do you think we should add a new Interface that we would test (as we did > > with NoConfigMerge for example ) then cast and call handleDryRun or add > > this method in Sampler interface ? > > Seems like a lot of work for a feature that's not likely to be much used. > > If I want to test a plan, I just run it with a single thread. > > > Thanks > > -- > > Regards > > Philippe >
