Projects

JExample

A JUnit extension that helps you to reuse fixtures and to pinpoint failures. Extends JUnit with depedencies between tests.

stickycode

Java by Convention Why "Sticky" well the sticky conventions let you build applications that don't need glue, it just sticks together, its "Sticky Code"

OceanRunner

A problem, with JUnit is that you CAN’T use multiple interesting Runners for a Test: OceanRunner tries to solve that problem. By offering an easy way to integrate “RunnersLike” class, named OceanModule, you may conjugate many behaviors of unit testing strategy. When you can use a single Runner for test, you may use many OceanModules.

junit-idea-plugin

A plugin for Intellij IDEA to support JUnit 4.

JavaStubs

Provides method stubbing for concrete Java classes, intended for use with JUnit 4.

Tools for Testing (TfT)

Tools for Testing (TfT) is a set of Java-classes to support the programmer in the use of Junit 4. Download the latest release here: http://tft.origo.ethz.ch/download Development is maintained in the Trac: https://sourceforge.net/apps/trac/tftest/

Tools for Testing

Tools for Testing creates a collection of helper-classes for the work with jUnit 4.

supercheckers

Supercheckers is a clone of the little-known board game of Kings Court. It is written in Java.

moxiemocks

Moxie is a library for creating mock objects in Java. It aims to have the "nicest" syntax of any Java mocking library: Concise - set up any expectation in one Java statement. Short method names, no anonymous inner classes, no need to "replay" mock objects. Refactorable - ... [More] method name/signature changes using refactoring tools will be reflected in your tests. Easy - integrates with JUnit 4 to automatically create and verify mocks on your test objects. (You can still do this manually.) Moxie was written after years of annoyance^H^H^H^H^H^H^H^H^Hexperience with JMock, EasyMock and Mockito, and aims to take lessons form each. [Less]

Selenium JUnit 4 Runner

This is a JUnit 4 class runner that: 1. Reduces some of the boiler-plate required to write integration tests for Selenium using JUnit 4 2. Makes it easier to implement re-usable custom method rules 3. Allows you write integration tests that run against multiple browsers