Before and After Suite execution hook in jUnit 4.x

by

Yes, it is possible to reliably run set up and tear down methods before and after any tests in a test suite. Let me demonstrate in code:

package com.test;

import org.junit.AfterClass;
import org.junit.BeforeClass;
import org.junit.runner.RunWith;
import org.junit.runners.Suite;
import org.junit.runners.Suite.SuiteClasses;

@RunWith(Suite.class)
@SuiteClasses({Test1.class, Test2.class})
public class TestSuite {

    @BeforeClass
    public static void setUp() {
        System.out.println("setting up");
    }

    @AfterClass
    public static void tearDown() {
        System.out.println("tearing down");
    }

}

So your Test1 class would look something like:

package com.test;

import org.junit.Test;


public class Test1 {
    @Test
    public void test1() {
        System.out.println("test1");
    }

}

…and you can imagine that Test2 looks similar. If you ran TestSuite, you would get:

setting up
test1
test2
tearing down

So you can see that the set up/tear down only run before and after all tests, respectively.

The catch: this only works if you’re running the test suite, and not running Test1 and Test2 as individual JUnit tests. You mentioned you’re using maven, and the maven surefire plugin likes to run tests individually, and not part of a suite. In this case, I would recommend creating a superclass that each test class extends. The superclass then contains the annotated @BeforeClass and @AfterClass methods. Although not quite as clean as the above method, I think it will work for you.

As for the problem with failed tests, you can set maven.test.error.ignore so that the build continues on failed tests. This is not recommended as a continuing practice, but it should get you functioning until all of your tests pass. For more detail, see the maven surefire documentation.

More Related Contents:

  1. How to Re-run failed JUnit tests immediately?
  2. How to mock private method for testing using PowerMock?
  3. Embedded MongoDB when running integration tests
  4. How to configure JPA for testing in Maven
  5. How to test code dependent on environment variables using JUnit?
  6. How to write junit tests for interfaces?
  7. Mockito – NullpointerException when stubbing Method
  8. junit & java : testing non-public methods [duplicate]
  9. What’s the difference between failure and error in JUnit?
  10. JUnit: how to avoid “no runnable methods” in test utils classes
  11. JUnit: new instance before invoking each @Test method. What are the benefits?
  12. How do I run JUnit tests from inside my Java application?
  13. Integration tests for AspectJ
  14. Conditionally ignoring tests in JUnit 4
  15. Test class with a new() call in it with Mockito
  16. Initialising mock objects – MockIto
  17. Surefire is not picking up Junit 5 tests
  18. Mockito : how to verify method was called on an object created within a method?
  19. How do you assert that a certain exception is thrown in JUnit tests?
  20. Getting “NoSuchMethodError: org.hamcrest.Matcher.describeMismatch” when running test in IntelliJ 10.5
  21. Using PowerMockito.whenNew() is not getting mocked and original method is called
  22. How do I add a new sourceset to Gradle?
  23. Is Java’s assertEquals method reliable?
  24. java.lang.Exception: No runnable methods exception in running JUnits
  25. Problem with deserialization of LocalDateTime in Junit test
  26. MimeMessage.saveChanges is really slow
  27. Why is my class not calling my mocked methods in unit test?
  28. Forming Mockito “grammars”
  29. Unable to run JUnit test with PowerMockRunner
  30. JUnit 4 @BeforeClass & @AfterClass when using Suites

Leave a Comment