JUnit 4.2

JUnit is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks.

• Summary of Changes
• Contents
• Installation
• Getting Started
• Documentation
• Known Defects

Summary of Changes with version 4.3

• Changes in array equality. Using assertEquals to compare array contents is now deprecated. In the future, assertEquals will revert to its pre-4.0 meaning of comparing objects based on Java's Object.equals semantics. To compare array contents, use the new, more reliable Assert.assertArrayEquals methods.
• The @Ignore annotation can now be applied to classes, to ignore the entire class, instead of individual methods.
• Originally, developers who wanted to use a static suite() method from JUnit 3.x with a JUnit 4.x runner had to annotate the class with @RunWith(AllTests.class). In the common case, this requirement has been removed. However, when such a class is wrapped with a JUnit4TestAdapter (which we believe is rare), the results may not be as expected.
• Improved error messages for array comparison("arrays first differed at element [1][0]")
• Bug fix: Inaccessible base class is caught at test construction time.
• Bug fix: Circular suites are caught at test construction time.
• Bug fix: Test constructors that throw exceptions are reported correctly.
• For committers and extenders
  • Sources now are in a separate "src" directory (this means a big break in the CVS history)
  • Improved documentation in Request, RunWith

Summary of Changes with version 4.2

• Bug fix: Inaccessible base class is caught at test construction time.
• Bug fix: Circular suites are caught at test construction time.
• Improved error messages for array comparison("arrays first differed at element [1][0]")
• Test constructors that throw exceptions are reported correctly.

Summary of Changes with version 4.1

• Bug fix: listeners now get a correct test running time, rather than always being told 0 secs.
• The @RunWith annotation is now inherited by subclasses: all subclasses of an abstract test class will be run by the same runner.
• The build script fails if the JUnit unit tests fail
• The faq has been updated
• Javadoc has been improved, with more internal links, and package descriptions added (Thanks, Matthias Schmidt!)
• An acknowledgements.txt file has been created to credit outside contributions
• The Enclosed runner, which runs all of the static inner classes of a given class, has been added to org.junit.runners.

Summary of Changes with version 4.0

The architecture of JUnit 4.0 is a substantial departure from that of earlier releases. Instead of tagging test classes by subclassing junit.framework.TestCase and tagging test methods by starting their name with "test", you now tag test methods with the @Test annotation.

Contents of the Release

Installation

1. unzip the junit4.3.zip file
2. add junit-4.3.jar to the CLASSPATH. For example: set classpath=%classpath%;INSTALL_DIR\junit-4.2.jar;INSTALL_DIR
3. test the installation by running java org.junit.runner.JUnitCore org.junit.tests.AllTests.

Notice: that the tests are not contained in the junit-4.3.jar but in the installation directory directly. Therefore make sure that the installation directory is on the class path

Getting Started

You find additional samples in the org.junit.samples package:

• SimpleTest.java - some simple test cases
• VectorTest.java - test cases for java.util.Vector

Documentation

JUnit Cookbook
    A cookbook for implementing tests with JUnit.
Javadoc
    API documentation generated with javadoc.
Frequently asked questions
    Some frequently asked questions about using JUnit.
License
    The terms of the common public license used for JUnit.

Test Infected - Programmers Love Writing Tests
    An article demonstrating the development process with JUnit.
JUnit - A cooks tour

Known Defects

• Multi-dimensional arrays are not processed correctly by assertEquals.