CustomJunit4RunnerJUnit4_4

Introduction

(Note This example works with JUnit 4.4 and later and it requires Java 5 or later. It will not work with the JUnit shipped with Eclipse. So add JUnit4.4.jar to your class path in Eclipse when using this code.)

This comes from a recent problem at a customer site. The customer had a number of automated tests written in JUnit. The tests were a mixture of unit tests and integration tests. To try and speed up the developer experience, we though that moving the integration-style tests into a separate source tree would solve the problem.

If we had been primarily working in Eclipse, this would not have been a problem. As it was, we were working in IntelliJ and while I’m sure what we wanted to do was easy if we knew how to do it, we did not. To move along the process, we decided to write a custom JUnit runner.

Here are a few assumptions:

We want to NOT run the integration tests by default in the IDE
We want to be able to run the integration tests in the IDE
We want to be able to run the integration tests using the automated build scripts
We want to be able to not run the integration tests using the automated build scrips
A test class’ test methods are either all integration tests or none of its methods are integration tests; we did not want to individually decide which tests were integration tests

We settled on a simple approach. If there is a system property defined calledExecuteIntegrationTests, we run the integration tests, if not, we ignore them.

Original Idea

The original idea was to use the @RunWith(…) annotation to use a custom JUnit4 Runner and then add to that an annotation @Integration to indicate something was an integration test. However, having both was redundant so we settled on simply specifying a custom runner, e.g.:

@RunWith(IntegrationTestIgnorer.class)
public class SomeClassThatHasIntegrationTests {
   @Test
   public void someTestMethod() {
   }
}

When this test is executed either:

All tests are ignored if the environment variableExecuteIntegrationTests is defined
All tests are executed if the environment variableExecuteIntegrationTests is not defined

To get integration tests to execute, simply add -DExecuteIntegrationTests to the command-line when running the JVM.

The Code

After many trials and opening up the JUnit 4.4. source, this is what we came up with: —- —-

IntegrationTestIgnorer

This class is both a Runner and holds on to a runner. The particular runner is determined by a factory class (RunnerFactory below). This class simply adds a level of indirection between the execution of a test and the selection of the particular JUnit runner used to execute tests in a given test class.

package com.om.runner;

import org.junit.internal.runners.InitializationError;
import org.junit.runner.Description;
import org.junit.runner.Runner;
import org.junit.runner.notification.RunNotifier;

public class IntegrationTestIgnorer extends Runner {
    Runner runner;

    public IntegrationTestIgnorer(Class<?> clazz) throws InitializationError {
        runner = RunnerFactory.createRunnerFor(clazz);
    }

    @Override
    public Description getDescription() {
        return runner.getDescription();
    }

    @Override
    public void run(RunNotifier runNotifier) {
        runner.run(runNotifier);
    }

    @Override
    public int testCount() {
        return runner.testCount();
    }
}

RunnerFactory.java

This class determines whether or not Integration tests should be skipped and the style of test class and then constructs an appropriate runner to run the tests (or ignore them).

There are 4 possibilities based on the following two items:

Are we or are we not skipping Integration tests (system property defined or not)
Are we using a JUnit 3 or JUnit 4 style test (class derives from TestCase or not)

package com.om.runner;

import junit.framework.TestCase;

import org.junit.internal.runners.InitializationError;
import org.junit.internal.runners.JUnit38ClassRunner;
import org.junit.internal.runners.JUnit4ClassRunner;
import org.junit.runner.Runner;

public class RunnerFactory {

    public static Runner createRunnerFor(Class<?> clazz) throws InitializationError {
        if (shouldSkipClass() && isSubclassOfTestCase(clazz)) {
            return new JUnit38TestMethodIgnorer(clazz);
        }

        if (shouldSkipClass() && !isSubclassOfTestCase(clazz)) {
            return new JUnit4TestMethodIgnorer(clazz);
        }

        if (!shouldSkipClass() && isSubclassOfTestCase(clazz)) {
            return new JUnit38ClassRunner(clazz);
        }

        return new JUnit4ClassRunner(clazz);
    }

    private static boolean isSubclassOfTestCase(Class<?> clazz) {
        return TestCase.class.isAssignableFrom(clazz);
    }

    public static boolean shouldSkipClass() {
        return System.getProperty("ExecuteIntegrationTests") == null;
    }

}

JUnit38TestMethodIgnorer.java

This class simply fires a “test ignored” message so that listeners know that each test was skipped. In IntelliJ and JUnit, their respective runners register listeners that select an icon in a tree viewer based on this message being fired. Also, by firing a message per test method, the progress bars will be updated correctly (as will test execution counts).

package com.om.runner;

import java.lang.reflect.Method;

import org.junit.internal.runners.JUnit38ClassRunner;
import org.junit.runner.Description;
import org.junit.runner.notification.RunNotifier;

public final class JUnit38TestMethodIgnorer extends JUnit38ClassRunner {
    private final Class<?> clazz;

    public JUnit38TestMethodIgnorer(Class<?> clazz) {
        super(clazz);
        this.clazz = clazz;
    }

    @Override
    public void run(RunNotifier notifier) {
        Method[] methods = clazz.getDeclaredMethods();
        for (Method method : methods) {
            if (isTestMethod(method)) {
                Description description = Description.createTestDescription(clazz, method.getName());
                notifier.fireTestIgnored(description);
            }
        }
    }

    private boolean isTestMethod(Method method) {
        return method.getParameterTypes().length == 0 && 
               method.getName().startsWith("test") && 
               method.getReturnType().equals(Void.TYPE);
    }
}

JUnit4TestMethodIgnorer.java

This test accomplishes the same thing in a somewhat easier manner than the JUnit 3 ignorer. There is a method to execute an individual test method, which this class simply overrides to fire an ignored test message. However, if all methods are ignored, the class will fail validation as defined in the base class JUnit4ClassRunner. So, this class also overrides the validate() method to make that error go away.

package com.om.runner;

import java.lang.reflect.Method;

import org.junit.internal.runners.InitializationError;
import org.junit.internal.runners.JUnit4ClassRunner;
import org.junit.runner.Description;
import org.junit.runner.notification.RunNotifier;

public class JUnit4TestMethodIgnorer extends JUnit4ClassRunner {
    public JUnit4TestMethodIgnorer(Class<?> clazz) throws InitializationError {
        super(clazz);
    }

    @Override
    protected void invokeTestMethod(Method method, RunNotifier notifier) {
        Description description = methodDescription(method);
        notifier.fireTestIgnored(description);
    }

    @Override
    protected void validate() {
    }
}

Writing a Custom JUnit 4 Test Runner