Yes, it’s Yet Another JUnit Antipatterns Update. This time, I’ve tried to apply all the feedback I received from the find folks on the JUnit mailing list. Specifically, I posted a notice about my last update on the list, and received an absolute flurry of responses from unit testing luminaries near and far.
As a result of all this, the JUnit Anti-patterns page has been overhauled yet again. The major changes are:
- Added section on using the wrong assert
- Expanded on the unexpected exceptions section
- Expanded on the multiple asserts section
- Avoided using the title “Refactorings”
- Linked to an explicit license
Renaissance Developer 