On Aug 3, 2007, at 7:55 PM, Kevin Menard wrote:
Then I suppose this would raise another topic. JUnit 3 is a bit of a
boar for testing exception. You basically have to try, catch, fail.
TestNG has a standard facility for testing for expected
exceptions. My
guess is that JUnit4 does as well, but I have nothing to back that up
with. There was some discussion some time ago about moving the
testing
framework. Have we hit that crossroad yet, or is that still for a
rainy
day?
This is certainly close to zero priority on my personal list. But I
have no objections to somebody else working on the switch to a newer
JUnit. I will only be against it if it turns out to be as disruptive
as the recent Maven migration.
Andrus
