Open Source Java Testing Tools

1. Cactus(http://jakarta.apache.org/cactus/index.html)

   Description:

   Cactus is a simple test framework for unit testing server-side java code (Servlets, EJBs, Tag Libs, Filters, ...) The intent of Cactus is to lower the cost of writing tests for server-side code. It uses JUnit and extends it.

2. Checkstyle(http://checkstyle.sourceforge.net/)

   Description:

   Checkstyle is a development tool to help programmers write Java code that adheres to a coding standard. By default it supports the Sun Code Conventions, but is highly configurable. It can be invoked with an ANT task and a command line program.

3. Cobertura(http://cobertura.sourceforge.net/)

   Description:

   Cobertura is a free Java tool that calculates the percentage of code accessed by tests. It can be used to identify which parts of your Java program are lacking test coverage. It is based on jcoverage.

4. Dbunit(http://dbunit.sourceforge.net/)

   Description:

   DbUnit is a JUnit extension (also usable from Ant) targeted for database-driven projects that, among other things, puts your database into a known state between test runs. This is an excellent way to avoid the myriad of problems that can occur when one test case corrupts the database and causes subsequent tests to fail or exacerbate the damage.

5. EasyMock + ClassExtension(http://www.easymock.org/)

   Description:

   EasyMock with class extension provides an easy, clean framework for creating mock-objects for classes and interfaces. The expected method calls and desired return values are specified, the code under test is run and then the expected behaviour is verified.

6. EclEmma(http://www.eclemma.org/)

   Description:

   EclEmma is a free Java code coverage tool for Eclipse, available under the Eclipse Public License. Internally it is based on the great EMMA Java code coverage tool, trying to adopt EMMA's philosophy for the Eclipse workbench.

7. Findbugs(http://findbugs.sourceforge.net/)

   Description:

   Findbugs is a static analysis tool to find bugs in Java programs.

8. Jester(http://jester.sourceforge.net/)

   Description:

   Jester finds code that is not covered by tests. Jester makes some change to your code, runs your tests, and if the tests pass Jester displays a message saying what it changed. Jester includes a script for generating web pages that show the changes made that did not cause the tests to fail. Jester is different than code coverage tools, because it can find code that is executed by the running of tests but not actually tested. However, Jester is not meant as a replacement for code coverage tools, merely as a complementary approach. Jester is for Java code and JUnit tests. Pester is Jester for Python code and PyUnit tests.

9. jMock(http://www.jmock.org/)

   Description:

   jMock is a library for testing Java code using mock objects. The jMock package makes it quick and easy to define mock objects, lets you define flexible constraints over object interactions, and is easy to extend.

10. JUnitPerf(http://www.clarkware.com/software/JUnitPerf.html)

    Description:

    JUnitPerf is a collection of JUnit test decorators used to measure the performance and scalability of functionality contained within existing JUnit tests.

11. PMD(http://pmd.sourceforge.net/)

    Description:

    PMD scans Java source code and looks for potential problems. It has plugins for JEdit, JBuilder, Netbeans/Forte/Sun ONE, IntelliJ IDEA, Maven, Ant, Eclipse, Gel, and Emacs.

12. StrutsTestCase for JUnit v1.9.5(http://strutstestcase.sourceforge.net/)

    Description:

    StrutsTestCase for JUnit is an extension of the standard JUnit TestCase class that provides facilities for testing code based on the Struts framework.

13. JEasyTest(https://jeasytest.dev.java.net/)

    Description:

    JEasyTest is an Eclipse IDE plugin created to simplify unit testing of code that is hard to test using standard mock objects frameworks, as for example code using legacy code.

14. djUnit(http://works.dgic.co.jp/djunit/index.html)

    Description:

    djUnit is a JUnit test runner, which generates coverage report and allows virtual mock objects. It integrates with Eclipse and Ant.

15. TagUnit(http://tagunit.sourceforge.net/)

    Description:

    In the same way that JUnit allows us to write unit tests for Java classes, TagUnit allows us to unit test JSP custom tags, inside the container. In essence, TagUnit is a tag library for testing custom tags within JSP pages.

16. JCoverage(http://java-source.net/open-source/code-coverage/jcoverage-gpl)

    Description:

    jcoverage/gpl is a free code-coverage tool for Java™ programmers that allows them to measure the effectiveness of their Java tests and how much of a software program's code has been tested. jcoverage/gpl identifies how many times each line of code in your application has been executed and you can see which parts of your software remain untested. After instrumenting your code and running your tests, a report is generated allowing you to view information coverage figures from a project level right down to the individual line of code. This process is called 'code coverage'.

17. Coverlipse(http://java-source.net/open-source/code-coverage/coverlipse)

    Description:

    An eclipse plugin for code coverage visualization of JUnit Tests. Supported coverages include block coverage and all-uses coverage (Data Flow Analysis).

18. CoverCode(http://java-source.net/open-source/code-coverage/codecover)

    Description:

    CodeCover is an extensible open source code coverage tool, with the following features:
    
     * Supports statement coverage, branch coverage, loop coverage and strict condition coverage (aka condition/decision coverage).
     * Performs source instrumentation for the most accurate coverage measurement.
     * CLI interface, for easy use from the command line.
     * Ant interface, for easy integration into an existing build process.
     * Fully integrated into Eclipse.
     * Customizable HTML and CSV report.
     * Per test case coverage measurement.
     * Fully integrated with JUnit for automatic recognition of test cases.
     * Live notification for manual test case recognition.
     * Boolean Analyzer which helps to find test cases to increase strict condition coverage.
     * Correlation Matrix to find redundant test cases and optimize your test suite.