Using different classloaders for different JUnit tests?

by

This question might be old but since this was the nearest answer I found when I had this problem I though I’d describe my solution.

Using JUnit 4

Split your tests up so that there is one test method per class (this solution only changes classloaders between classes, not between methods as the parent runner gathers all the methods once per class)

Add the @RunWith(SeparateClassloaderTestRunner.class) annotation to your test classes.

Create the SeparateClassloaderTestRunner to look like this:

public class SeparateClassloaderTestRunner extends BlockJUnit4ClassRunner {

    public SeparateClassloaderTestRunner(Class<?> clazz) throws InitializationError {
        super(getFromTestClassloader(clazz));
    }

    private static Class<?> getFromTestClassloader(Class<?> clazz) throws InitializationError {
        try {
            ClassLoader testClassLoader = new TestClassLoader();
            return Class.forName(clazz.getName(), true, testClassLoader);
        } catch (ClassNotFoundException e) {
            throw new InitializationError(e);
        }
    }

    public static class TestClassLoader extends URLClassLoader {
        public TestClassLoader() {
            super(((URLClassLoader)getSystemClassLoader()).getURLs());
        }

        @Override
        public Class<?> loadClass(String name) throws ClassNotFoundException {
            if (name.startsWith("org.mypackages.")) {
                return super.findClass(name);
            }
            return super.loadClass(name);
        }
    }
}

Note I had to do this to test code running in a legacy framework which I couldn’t change. Given the choice I’d reduce the use of statics and/or put test hooks in to allow the system to be reset. It may not be pretty but it allows me to test an awful lot of code that would be difficult otherwise.

Also this solution breaks anything else that relies on classloading tricks such as Mockito.

More Related Contents:

  1. Conditionally ignoring tests in JUnit 4
  2. Test class with a new() call in it with Mockito
  3. Run single test from a JUnit class using command-line
  4. Mockito : how to verify method was called on an object created within a method?
  5. How to tell a Mockito mock object to return something different the next time it is called?
  6. Get name of currently executing test in JUnit 4
  7. How to test code dependent on environment variables using JUnit?
  8. How to run all tests belonging to a certain Category in JUnit 4
  9. How to set JVM parameters for Junit Unit Tests?
  10. How to mock new Date() in java using Mockito
  11. How to write junit tests for interfaces?
  12. junit & java : testing non-public methods [duplicate]
  13. How to verify that a specific method was not called using Mockito?
  14. JUnit 4: Set up things in a test suite before tests are run (like a test’s @BeforeClass method, just for a test suite)
  15. How to test a Jersey REST web service?
  16. Injecting @Autowired private field during testing
  17. java.lang.NoClassDefFoundError in junit
  18. Why are my mocked methods not calld when executing a unit test?
  19. Forming Mockito “grammars”
  20. differences between 2 JUnit Assert classes
  21. Concurrent JUnit testing
  22. Testing against Java EE 6 API
  23. How do I unit test jdbc code in java? [closed]
  24. How can I unit test void functions?
  25. Java verify void method calls n times with Mockito
  26. JUnit: new instance before invoking each @Test method. What are the benefits?
  27. Junit Test of Setters and Getters of Instance Variables
  28. Why are my mocked methods not called when executing a unit test?
  29. JUnit test with dynamic number of tests
  30. Easier DynamoDB local testing

Leave a Comment