JUnit 3.2

JUnit is a simple framework to write repeatable tests. JUnit can be used with JDK 1.1.* and JDK 1.2.*.

• Summary of Changes
• Contents
• Installation
• Getting Started
• Documentation
• Extending JUnit
• License

Summary of Changes between 3.1 and 3.2

• Fixed bug in the handling of inherited test methods.
• The junit.swing.TestRunner support selective test execution. A Test Browser shows the contents of the entered test suite as a tree and you can select the test case to be run. The Test Browser can be launched from JUnit menu.
• The history file of junit.swingui.TestRunner is stored in .junit on non Windows platforms.
• Support for rerunning a failed test was previously only available inside VisualAge for Java. It is now generally available when using the LoadingTestRunners.
• The junit.textui.TestRunner exits with -1 when the test run fails.

Summary of Changes between 2.1 and 3.1

JUnit Framework

• TestSuite now extracts inherited test methods. The test extraction stops at the first class that doesn't implement Test.
• Added support for TestListeners. A TestListeners observes changes to the TestResult. It enables to have multiple observers on the same result and allowed us to delete the TestResult subclasses (parallel class hierarchy) as the TestRunners now implement TestListener. It also allows clients to generate additional kinds of test run feedback.
• Added an ExceptionTestCase class. A TestCase that expects a particular exception to be thrown.
• Fixed TestSetup so that errors in setUp are caught and reported correctly.
• Assertion checks where moved from TestCase into a separate Assert class. This enables programming by contract.
• Added support for protected blocks. A protected block has to implement the Protectable interface. We used it to factor out a common template method to run tests. To implement your own protected block that logs thrown exceptions, pass a Protectable to TestResult.runProtected().
• Clarified and deprecated method names in TestResult: testErrors, testFailures and runTests are now called errorCount, failureCount and runCount.
• TestCase.getResult got removed you can add access to the current TestResult in your own TestCase subclasses.
• TestCase.setUp() and tearDown() now throw a Throwable, so you can allow exceptions in setUp() to propagate.

TestRunner

• There is a new version of a Swing based graphical TestRunner. It supports a combo box with a persistent history of ran test suites. You can start it with:

    java junit.swingui.TestRunner
There is also a LoadingTestRunner for Swing. The Swing TestRunner requires Swing 1.1 (javax.swing package structure) or jdk 1.2.
• Some common code among the TestRunners was moved into the package junit.util.
• The batch TestRunner unit.textui.TestRunner can now be given a PrintStream to output the results to.
• The batch TestRunner can be given a class to run directly. To start the batch runner from your main you can write:

public static void main(String args[]) {
  junit.textui.TestRunner.run(MoneyTest.class);
}

Documentation

• There is a new article: JUnit a cook's tour included.

Release

• We no longer provide a .dat file for VAJ users. You install JUnit into VAJ by importing the resources from the junit.jar and the sources from the src.zip files.

Summary of changes between 1.0 and 2.1

Contents of the Release

Installation

1. unzip the junit.zip file
2. add junit.jar to the CLASSPATH. For example: set classpath=%classpath%;INSTALL_DIR\junit3\junit.jar
3. test the installation by using either the batch or the graphical TestRunner tool to run the tests that come with this release. All the tests should pass OK.
• for the batch TestRunner type:

    java junit.textui.TestRunner junit.samples.AllTests
• for the graphical TestRunner type:

    java junit.ui.TestRunner junit.samples.AllTests
• for the Swing based graphical TestRunner type:

    java junit.ui.TestRunner junit.samples.AllTests

Getting Started

You find additional samples in the junit.samples package:

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

Which TestRunner to use?

• a textual TestRunner - it is the fastest to launch and can be used when you don't need a red green success indication.
• graphical TestRunners - they show a simple graphical dialog to enter the test and provide some graphical progress indication. The graphical TestRunners come in two flavors:
• the classical TestRunner - it needs to be restarted after every change to your classes. Otherwise you will run your tests with the old code. The exception is when running JUnit from inside VisualAge for Java. In this case the integrated development environment takes care of updating the environment so that you don't have to restart the TestRunner.
• the so called LoadingTestRunner, it can reload your classes from the class path for each run and therefore doesn't have to be restarted.

Documentation

JUnit Cookbook
    A cookbook for implementing tests with JUnit.
Test Infected - Programmers Love Writing Tests
    An article demonstrating the development process with JUnit.
JUnit - A cooks tour
Javadoc
    API documentation generated with javadoc.
Using JUnit with VisualAge for Java
    Hints about how to use JUnit in the VisualAge for Java environment.
Frequently asked questions
    Some frequently asked questions about using JUnit.

Extending JUnit

• TestDecorator - A decorator for Test. You can use it as the base class for implementing decorators to extend test cases.
• ActiveTest - A Decorator which runs each test in a separate thread.
• TestSetup - A Decorator to set up and tear down additional fixture state. Subclass TestSetup and insert it into your tests when you want to set up additional state once before the tests are run.
• ExceptionTestCase - A TestCase that expects a particular Exception to be thrown.