- Participate in the discussion forum.
- "An early look at JUnit 4" (Elliotte Rusty Harold, developerWorks, September 2005): Elliotte Harold takes JUnit 4 out for a spin.
- "In pursuit of code quality: JUnit 4 vs. TestNG" (Andrew Glover, developerWorks, August 2006): Is it true that JUnit 4 has borrowed all of its best tricks from TestNG?
- "TestNG makes Java unit testing a breeze" (Filippo Diotalevi, developerWorks, January 2005): TestNG isn't just powerful, innovative, extensible, and flexible; it also illustrates an interesting application of Java annotations.
- "Annotations in Tiger, Part 1: Add metadata to Java code" (Brett McLaughlin, developerWorks, September 2004): Brett McLaughlin explains why metadata is so useful, introduces you to annotations in the Java language, and delves into Java 5's built-in annotations.
- "Classworking toolkit: Annotations vs. configuration files" (Dennis Sosnoski, developerWorks, August 2005): Dennis Sosnoski explains why configuration files still have their uses, especially for aspect-like functions that cut across the source-code structure of an application.
- "JUnit Reloaded" (Ralf Stuckert, Java.net, December 2006): Compares JUnit 4 to earlier versions.
- "JUnit 4 you" (Fabiano Cruz, Fabiano Cruz's Blog, June 2006): An overview of tool and IDE support for JUnit 4.
- "Limiting asserts in test cases" (thediscoblog.com): A best practice for JUnit, TestNG, or any other framework that fails fast.
- "DbUnit with JUnit 4" (testearly.com): Just because JUnit 4 is different doesn't mean you can't use it with extension frameworks built for older versions of JUnit.
- "Using JUnit extensions in TestNG" (Andrew Glover, thediscoblog.com, March 2006): Just because a framework claims to be a JUnit extension doesn't mean it can't be used within TestNG.
-
In pursuit of code quality series (Andrew Glover, developerWorks): See all the articles in this series ranging from code metrics to testing frameworks to refactoring.


