Andrzej Doyle Andrzej Doyle - 2 months ago 11x
Java Question

Conditionally ignoring tests in JUnit 4

OK, so the

annotation is good for marking that a test case shouldn't be run.

However, sometimes I want to ignore a test based on runtime information. An example might be if I have a concurrency test that needs to be run on a machine with a certain number of cores. If this test were run on a uniprocessor machine, I don't think it would be correct to just pass the test (since it hasn't been run), and it certainly wouldn't be right to fail the test and break the build.

So I want to be able to ignore tests at runtime, as this seems like the right outcome (since the test framework will allow the build to pass but record that the tests weren't run). I'm fairly sure that the annotation won't give me this flexibility, and suspect that I'll need to manually create the test suite for the class in question. However, the documentation doesn't mention anything about this and looking through the API it's also not clear how this would be done programmatically (i.e. how do I programatically create an instance of
or similar that is equivalent to that created by the

If anyone has done something similar in the past, or has a bright idea of how else I could go about this, I'd be happy to hear about it.


The JUnit way is to do this at run-time is org.junit.Assume.

 public void beforeMethod() {
     // rest of setup.

You can do it in a @Before method or in the test itself, but not in an @After method. If you do it in the test itself, your @Before method will get run.

An assumption failure causes the test to be ignored.

Edit: To compare with the @RunIf annotation from junit-ext, their sample code would look like this:

public void calculateTotalSalary() {
    assumeThat(Database.connect(), is(notNull()));
    //test code below.

Not to mention that it is much easier to capture and use the connection from the Database.connect() method this way.