JUnit 4 final is released. JUnit 4 adds support for annotations. However it is not yet clear (to me) if it addresses the main concerns I previously had with JUnit (pretty much the same concerns many others have voiced). I heave heard tell that JUnit 4 will include groups of some sort but have not heard anything about the class instantiation "issue" (my term for it, others debate that its a problem - there is a new @BeforeClass and @AfterClass that can help with the current static initializer requirement - and that is great - but that is different from the concern about creating a class instance for every test).
Both Cedric and developerWorks have previous early reviews of what JUnit 4 has/does, but those sneek peaks were both quite some time back and the JUnit site does not yet have a CHANGELOG up (nor has it been changed in any regard at all to note the release - yet).
All in all I am a huge fan of JUnit and have to say props to the crew for providing the great utility over the years. It has been invaluable to me on many projects. However, in fairness it seems that TestNG (which just rolled 4.5) is still possibly ahead of it. TestNG has grouping, does not do the one instance per test thing, has had annotation for a while and more (Many people have commented - such as in the TSS threads - that JUnit 4 is just an attempt to catch up a bit with TestNG - but its not quite there yet.)
Comments
RE: Junit 4 final arrives
You know, the inertia of JUnit is really starting to piss me off. Unfortunately, like so many things, it is tightly coupled to the inertia of JDK1.4.x that it seems we just can't escape from. Over the course of 36 months or so, I don't see JUnit surviving the "attack" from TestNG, it just seems soooo far away at this point.