We’ve previously covered many of the shortcomings of JUnit 3. It should be pretty obvious by now that it’s not really a tool suitable for many types of testing. Yet it’s wildly popular.
A large part of this popularity is due to the JUnit ecosystem. Despite its awkwardness and lack of extensibility, developers have come up with remarkable workarounds and extensions in order to twist JUnit’s proverbial arms into satisfying more niche requirements than bare-bones unit testing.
Some of these extensions include frameworks that provide their own testing harnesses, such as the ubiquitous Spring framework. Others include base classes that enhance the set of asserts provided by JUnit. Many provide additional frameworks to ease the ...
No credit card required