[Junit-trackers] [ junit-Feature Requests-1607483 ] Make it easier to extend the existing Runners

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

Feature Requests item #1607483, was opened at 2006-12-02 11:41
Message generated for change (Comment added) made by dsaff
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=365278&aid=1607483&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: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Nat Pryce (npryce)
Assigned to: Nobody/Anonymous (nobody)
Summary: Make it easier to extend the existing Runners

Initial Comment:
I just added a JUnit 4 integration package to jMock 2.  
I needed to extend or plug into an existing Runner class to change the way it runs tests so that it automatically checked that all the test's expectations on its mock objects were satisfied before tearing down the fixture.

To do this I had to subclass the Runner classes in JUnit's internal packages which I'm a bit uncomfortable about.  I'd like the existing Runners be extensible or have known plug-in points to change the way that they run tests.


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

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

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

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

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