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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
