Like you said, it fails because the arguments are different. Take a look at the test below and you’ll see that the second test method will fail because the status in your MyClass instance is different from SomeStatus that you passed in the matcher. public class MatcherTest { class MyClass{ private String status; MyClass(String status) … Read more
As noted in another answer, if you don’t care about the order, you might do best to change the interface so it doesn’t care about the order. If order matters in the code but not in a specific test, you can use the ArgumentCaptor as you did. It clutters the code a bit. If this … Read more
You need to use mockito-inline version 3.4.0 or higher and remove mockito-core from your dependencies (mockito-inline depends on mockito-core so it will be retrieved automatically). That way, you will be using mockito static mocking correctly, but it wouldn’t solve the exception that you posted. To fix it, you need to remove all dependencies of powermock … Read more
First thing, you should be passing spy in as the constructor argument. That aside, here’s how you could do it. public class ResultCaptor<T> implements Answer { private T result = null; public T getResult() { return result; } @Override public T answer(InvocationOnMock invocationOnMock) throws Throwable { result = (T) invocationOnMock.callRealMethod(); return result; } } Intended … Read more
I got this exception even though I had a public method annotaded with @Test. Turned out was importing org.junit.jupiter.api.Test, I changed to org.junit.Test and it worked fine.
The alternative is to use the @Mock annotation since then Mockito can use type reflection to find the generic type: public class MyTest { @Mock private ArrayList<String> mockArrayList; … public void setUp() { MockitoAnnotations.initMocks(this); } public void testMyTest() { when(mockArrayList.get(0)).thenReturn(“Hello world”); String result = mockArrayList.get(0); assertEquals(“Should have the correct string”, “Hello world”, result); verify(mockArrayList).get(0); } … Read more
It looks like you both want to mock what happens when userService.getUserById() is called, and also verify that setPasswordChangeRequired(true) is called on that returned object. You can accomplish this with something like: UserService userService = mock(UserService.class); User user = mock(User.class); when(userService.getUserById(anyLong())).thenReturn(user); … // invoke the method being tested … verify(user).setPasswordChangeRequired(true);
I got around this by upgrading to the latest version of mockito. Currently it is: testImplementation “org.mockito:mockito-core:2.25.1” After that I had some build errors which was resolved by selecting File->Invalidate Caches / Restart…
You could refactor MyClass so that it uses dependency injection. Instead of having it create an AnythingPerformerClass instance you could pass in an instance of the class to the constructor of MyClass like so : class MyClass { private final AnythingPerformerClass clazz; MyClass(AnythingPerformerClass clazz) { this.clazz = clazz; } public boolean performAnything() { return clazz.doSomething(); … Read more
From what I read on “Issue 53” of mockito (https://code.google.com/p/mockito/issues/detail?id=53) , my code was experiencing a problem due to the validation framework involved in Mockito. Precisely the following code was causing the exception per se. private ConstantNode getConstantNode(NumericalValue value){ ConstantNode node = Mockito.mock(ConstantNode.class); Mockito.when(node.evaluate()).thenReturn(value); Mockito.when(node.toString()).thenReturn(value.toString()); return node; } If you remember from my code, the … Read more