[Junit-trackers] [ junit-Feature Requests-1648138 ] Expose TextListener as API

[SourceForge.net <no...@so...>]

Feature Requests item #1648138, was opened at 2007-01-30 19:00
Message generated for change (Settings changed) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=365278&aid=1648138&group_id=15278

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Expose TextListener as API

Initial Comment:
The TextListener used by default by JUnitCore provides an important and public functionality.  Custom extensions should be able to use the TextListener in custom ways, while being able to track any future changes to the output format.

(Submitted by dsaff, who's login appears to have been forgotten)

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2009-12-01 02:20

Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: David Saff (dsaff)
Date: 2009-11-16 17:52

Message:
This tracker is being shut down.  Please move this item to
http://github.com/KentBeck/junit/issues

----------------------------------------------------------------------

Comment By: Alex (toalexsmail)
Date: 2008-03-12 21:31

Message:
Logged In: YES 
user_id=2034775
Originator: NO

I have related suggestion.

Currently TextListener on every event simply writes to standard output
(or to PrintWriter). If junits or application aslo writes its logs to
standard output then this output is mixed. For example, failures will
be written inside the logs of the application and not in the end.
Moreover, if there is some activity in @AfterClass that also prints to
the standard output than this will be written down AFTER summary of
the Junit.

I have partial solution to this situation. TextListener (or a new
class, say ConsoleListener) should create new PrintWriter(new
StringWriter()) and collect the result their. On testRunFinished() it
should flush the information from StringWriter to the PrintStream that
received in the constructor (String.out for example).
This solution doesn't solve situation when there is some writing to
the standard output in @AfterClass.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=365278&aid=1648138&group_id=15278