The accepted answer has fallen a little out of date regarding the links so it’s worth mentioning the various solutions directly. To fix this problem do one of the following: 1 – Specifiy a javaagent Add this to your JUnit execution environment (for your version): -javaagent:path/to/your/jmockit/jmockit-0.998.jar 2 – configure the Surefire plugin in Maven to … Read more
PowerMock is another mock framework that extends EasyMock and Mockito. With PowerMock you can easily remove unwanted behavior from a class, for example a static initializer. In your example you simply add the following annotations to your JUnit test case: @RunWith(PowerMockRunner.class) @SuppressStaticInitializationFor(“some.package.ClassWithStaticInit”) PowerMock does not use a Java agent and therefore does not require modification … Read more
One way is using reflection get rid of final modifier from the field and then replace the LOGGER field with Mocked one public class Class1Test { @Test public void test() throws Exception { Logger logger = Mockito.mock(Logger.class); Mockito.when(logger.isInfoEnabled()).thenReturn(false); setFinalStatic(Class1.class.getDeclaredField(“LOGGER”), logger); Class1 cls1 = new Class1(); assertFalse(cls1.demoMethod()); } static void setFinalStatic(Field field, Object newValue) throws Exception … Read more
It sounds like you may want to be using the .expects(1) type methods that mock frameworks usually provide. Using mockito, if you were testing a List and wanted to verify that clear was called 3 times and add was called at least once with these parameters you do the following: List mock = mock(List.class); someCodeThatInteractsWithMock(); … Read more
Update Sep 2019: The only mocking framework supported (by default) by Spring Boot is Mockito. If you use Spring, the answer is quite obvious. I’d say the competition is between JMockit and PowerMock, then Mockito. I’d leave “plain” jMock and EasyMock because they use only proxy & CGLIB and do not use Java 5 instrumentation … Read more