I think Peter is referring to the Test Beans stuff. Yes, it's beyond
1.9.1 -- it will probably go into the new release (1.10?). It's actually
a work-in-progress: as it stands now it should allow you to write Test
Elements with (mostly) no GUI coding -- not only Samplers, but generally
any test
Ok, so here's the thing. If you have a controller that does nothing but return null,
a loop
controller is going to continue searching for a sub-controller with a sampler to
return. If you're
controller returned a sampler, then null, then a sampler, then null, etc (like a
normal controller
Hi, Mike.
All things considered, I'm inclined to agree. And it's not creating a
problem for me at the moment. My NullSampler.sample(Entry) just returns
null, but I wonder if I'll have to modify that when I start plugging in
listeners.
However, since I've invested a little time on this issue,
have you looked at the new method for creating
samplers? jordi and sebastian have been working on it,
so you may want to take a look at that.
peter lin
--- Jerry Pulley [EMAIL PROTECTED] wrote:
Hi, Mike.
All things considered, I'm inclined to agree. And
it's not creating a
problem for
Hi, Peter.
No, I haven't, but it sounds like something I should peek at. I'm
considering having a team at work write some new functional- and
stress-testing components. Our current setup is built around JMeter
v1.7 but given the improvements that have accumulated since then we'll
probably do
I recently encountered some problems with the design of a controller,
and discussed them with M. Stover in the TriggeredController design
thread on jmeter-user. Here's what Mike said about
GenericController.next():
The semantics of the next() method are supposed to be like so:
returns
