Recently spotted via Google: IBM developerWorks has recently published a new article on... JUnit Antipatterns! The article is quite a good read, as it covers different ground to the Exubero JUnit Antipatterns article. I'll probably update the Exubero article at some stage to refer to the developerWorks article, and possibly adapt some of its content.

I've updated the JUnit AntiPatterns article after receiving a number of emails giving feedback on suggested improvements and new anti-patterns. I've made the following changes: Added sections for Misuse of Assertions and Redundant Assertions, and reorganised the anti-patterns that relate to assertions. Anti-pattern examples and the refactored solutions are now styled differently.

I've updated the JUnit AntiPatterns article with a new anti-pattern: Multiple Assertions.

JUnit AntiPatterns is an article on JUnit worst practices that I have written, in response to some scary examples of software "engineering" that I encountered during code reviews. Feedback is always welcome!