Opinions wanted - revising the Assertion Results listener

[kc...@360commerce.com]

I'd like to revise the Assertion Results listener, but I want to get
some other people's opinions first.

I don't like the fact that the Assertion Results listener uses the
same "Write All Data to a File" interface that the other listeners do.
Currently, this listener writes the exact same results as any of the
other listeners.  Unfortunately, unless you are in "functional
testing" mode, the assertion results won't even be written.  Among
other things, this means that you can not use this listener to look at
stored assertion results.  (This is the default behavior.  I have
recently implemented a change that would allow one to capture the
assertion results, but this is not yet in an official build.)

What I'm most interested in is recording details about any
errors/failures that occur.  On these occasions, I'd like to gather as
much data as I can.

Basically, I'm suggesting that we revise the Assertion Results
listener to be more like a "Problem Recorder."  When problems occur,
it would write detailed data about those problems (and just the
problems) to disk.  It can also display some subset of this data on
the UI.

If people prefer it, I could just write a separate "Problem Recorder."
However, it seems to me that the intent of the "Assertion Results"
listener is to highlight problems, and I would prefer not to confuse
people by adding a listener that was quite similar to an existing one.

Please indicate whether you have a strong opinion on whether we should
modify the existing listener or create a new one.

Thanks,
Keith



---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org

Re: Opinions wanted - revising the Assertion Results listener

[Mike Stover <ms...@apache.org>]

This sounds like an enhancement I wanted a while back.  I thought I wrote it up, but I guess I 
didn't.

I think there are two separate issues here.  One, it would be nice to be able to configure the 
logging to only log errors.  This could be a configurable aspect - and of course it'd be nice to 
be able to configure it for each listener.  Two, it would be nice to be able override the 
"functional testing" logging behavior at the listener level.

If those two abilities combined correctly, you'd get exactly the behavior you wanted out of the 
Assertion Results Listener (this listener could default to this behavior for convenience).  All 
that's required is A) the ability to override logging settings in ResultCollector, and B) a new 
setting indicating that only errors are to be logged.

I hope that makes sense.  In any case, I agree that the current Assertion Results Listener 
should just be changed rather than build a new one.

-Mike

On 30 Jan 2003 at 14:36, kcassell@360commerce.com wrote:

> 
> 
> I'd like to revise the Assertion Results listener, but I want to get
> some other people's opinions first.
> 
> I don't like the fact that the Assertion Results listener uses the
> same "Write All Data to a File" interface that the other listeners do.
> Currently, this listener writes the exact same results as any of the
> other listeners.  Unfortunately, unless you are in "functional
> testing" mode, the assertion results won't even be written.  Among
> other things, this means that you can not use this listener to look at
> stored assertion results.  (This is the default behavior.  I have
> recently implemented a change that would allow one to capture the
> assertion results, but this is not yet in an official build.)
> 
> What I'm most interested in is recording details about any
> errors/failures that occur.  On these occasions, I'd like to gather as
> much data as I can.
> 
> Basically, I'm suggesting that we revise the Assertion Results
> listener to be more like a "Problem Recorder."  When problems occur,
> it would write detailed data about those problems (and just the
> problems) to disk.  It can also display some subset of this data on
> the UI.
> 
> If people prefer it, I could just write a separate "Problem Recorder."
> However, it seems to me that the intent of the "Assertion Results"
> listener is to highlight problems, and I would prefer not to confuse
> people by adding a listener that was quite similar to an existing one.
> 
> Please indicate whether you have a strong opinion on whether we should
> modify the existing listener or create a new one.
> 
> Thanks,
> Keith
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> 



--
Michael Stover
mstover1@apache.org
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org