JUnit.org Resources for Test Driven Development

Cargo-itest is a integration test utility that is based on the JUnit testing
framework. It allows you to easily create an integration test with as less configuration possible.
It even provides you with a default tests that can be used out of the box:

1. AbstractDefaultDeploymentTest
2. AbstractDefaultHibernateDeploymentTest
3. AbstractDefaultNoDbDeploymentTest

Some main features:

Cargo-itest is a integration test utility that is based on the JUnit testing
framework. It allows you to easily create an integration test with as less configuration possible.
It even provides you with a default tests that can be used out of the box:

1. AbstractDefaultDeploymentTest
2. AbstractDefaultHibernateDeploymentTest
3. AbstractDefaultNoDbDeploymentTest

Some main features:

Both HOWTOs assume the user knows Java, but not JUnit.

Available at http://pub.admc.com/howtos/junit .

Besides explaining basic usage, the 3.x Howto explains the tricky aspects of 3.x, such as organizing suites and making test classes testrunner-friendly.

Besides explaining basic usage, the 4.x Howto covers good test design and the distinction between JUnit failures and errors.

With the help of T2 utility we can do automated testing with JUnit (yes!). T2 itself is a powerful automated testing utility for Java. It's free (GPL). Using it is quite easy. It can be used as simply as a library from a JUnit test. Check out the quick tutorial here.

This is a quick JUnit tutorial for new Java programmers: here.

Everyone wants to reuse their test code. Reusing test code for functional tests is harder, as tests navigate through many pages in an application. This also means that parts of the tests are similar. This article talks about how you can abstract screens in your application using the Screen Object Pattern.

Reusing Functional Tests - Part 1

Short and fast introduction to JUnit 4 new features. It shows "annotation based testing", "new exception handling mechanism", "usage of @ignore and timeouts", "new assertion statements" and "usage of JUnit4TestAdapter class" in JUnit 4. It takes only 60 seconds to have a look at. Enjoy it.
JUnit in 60 Seconds

To someone who is new to unit testing, the idea of mock objects can be confusing to say the least. However in this tutorial, we will focus on the concept of mocking in general. What is a mock object? What is it used for? Why can't I mock object XYZ? Let's look into these questions and maybe clear a bit of the air on the use of mock objects.
The Concept of Mocking

Ok...Ok...I get it, I should write unit tests. What exactly is a unit test? How do you write a unit test? How do I handle dependencies? And how is writing more code going to make my existing code better? This tutorial will show you how.
Unit testing with JUnit and EasyMock

JUnit is increasingly being used in scientific case studies. That's because it is comparatively small, well-known, and self-contained. For anyone who is interested in a detailed design documentation of how JUnit 3.8 works, I have documented its design. I chose JUnit 3.8 because the move to annotations in 4.0 may have made JUnit more convenient to use, but the design less clear (in object-oriented terms). JUnit is not the only common case study, JHotDraw is another.