ChatGPT解决这个技术问题 Extra ChatGPT

Using Mockito to mock classes with generic parameters

Is there a clean method of mocking a class with generic parameters? Say I have to mock a class Foo<T> which I need to pass into a method that expects a Foo<Bar>. I can do the following easily enough:

Foo mockFoo = mock(Foo.class);
when(mockFoo.getValue).thenReturn(new Bar());

Assuming getValue() returns the generic type T. But that's going to have kittens when I later pass it into a method expecting Foo<Bar>. Is casting the only means of doing this?

Why use foo and bar over more meaningful names. Just created a whole load of confusion for a lot of people.
@Kaigo it's quite typical in programming examples to use foo, bar and baz, especially when anonymizing real-world examples to hide confidential details. now, I'm more concerned with the fact that OP used the phrase "that's going to have kittens"...literally never heard anyone say that before ;)
Everyone knows that "having kittens" is bad thing for code to be doing, even if it's pretty great for cats. :--)

o
osundblad

I think you do need to cast it, but it shouldn't be too bad:

Foo<Bar> mockFoo = (Foo<Bar>) mock(Foo.class);
when(mockFoo.getValue()).thenReturn(new Bar());

Yes but you still have a warning. Is that possible to avoid the warning?
@SuppressWarnings("unchecked")
I think this is fully acceptable since we are talking about a mock object in a unit test.
@demaniak It doesn't work at all. Argument matchers can't be used in that context.
@demaniak That will compile just fine, but when running the test it will throw InvalidUseOfMatchersException (which is a RuntimeException)
S
Siddhant Saraf

One other way around this is to use @Mock annotation instead. Doesn't work in all cases, but looks much sexier :)

Here's an example:

@RunWith(MockitoJUnitRunner.class)
public class FooTests {

    @Mock
    public Foo<Bar> fooMock;
    
    @Test
    public void testFoo() {
        when(fooMock.getValue()).thenReturn(new Bar());
    }
}

The MockitoJUnitRunner initializes the fields annotated with @Mock.


this is deprecated in 1.9.5. :( Seems much cleaner to me.
@CodeNovitiate I couldn't find any deprecation annotations on MockitoJUnitRunner and Mock in 1.9.5. So, what is deprecated? (Yes, org.mockito.MockitoAnnotations.Mock is deprecated, but you should use org.mockito.Mock instead)
Well done, this worked perfectly for me. It's not just "sexier", it avoids a warning without using SuppressWarnings. Warnings exist for a reason, it's better to not be in the habit of suppressing them. Thanks!
There is one thing I don't like about using @Mock instead of mock(): the fields are still null during construction time, so I cannot insert dependencies at that time and cannot make the fields final. The former can be solved by a @Before-annotated method of course.
For initiation just call MockitoAnnotations.initMocks(this);
K
Konrad Borowski

You could always create an intermediate class/interface that would satisfy the generic type that you are wanting to specify. For example, if Foo was an interface, you could create the following interface in your test class.

private interface FooBar extends Foo<Bar>
{
}

In situations where Foo is a non-final class, you could just extend the class with the following code and do the same thing:

public class FooBar extends Foo<Bar>
{
}

Then you could consume either of the above examples with the following code:

Foo<Bar> mockFoo = mock(FooBar.class);
when(mockFoo.getValue()).thenReturn(new Bar());

Provided Foo is an interface or non-final class, this appears to be a reasonably elegant solution. Thanks.
I updated the answer to include examples for non-final classes as well. Ideally you would be coding against an interface, but that's not always going to be the case. Good catch!
a
acdcjunior

Create a test utility method. Specially useful if you need it for more than once.

@Test
public void testMyTest() {
    // ...
    Foo<Bar> mockFooBar = mockFoo();
    when(mockFooBar.getValue).thenReturn(new Bar());

    Foo<Baz> mockFooBaz = mockFoo();
    when(mockFooBaz.getValue).thenReturn(new Baz());

    Foo<Qux> mockFooQux = mockFoo();
    when(mockFooQux.getValue).thenReturn(new Qux());
    // ...
}

@SuppressWarnings("unchecked") // still needed :( but just once :)
private <T> Foo<T> mockFoo() {
    return mock(Foo.class);
}

Could extend your answer to make a general utility method passing in the class you want to mock.
@WilliamDutton static <T> T genericMock(Class<? super T> classToMock) { return (T)mock(classToMock); } it doesn't even need a single suppression :) But be careful, Integer num = genericMock(Number.class) compiles, but throws ClassCastException. This is only useful for the most common G<P> mock = mock(G.class) case.
T
Tobias Uhmann

I agree that one shouldn't suppress warnings in classes or methods as one could overlook other, accidentally suppressed warnings. But IMHO it's absolutely reasonable to suppress a warning that affects only a single line of code.

@SuppressWarnings("unchecked")
Foo<Bar> mockFoo = mock(Foo.class);

M
M. Justin

As the other answers mentioned, there's not a great way to use the mock() & spy() methods directly without unsafe generics access and/or suppressing generics warnings.

There is currently an open issue in the Mockito project (#1531) to add support for using the mock() & spy() methods without generics warnings. The issue was opened in November 2018, but there aren't any indications that it will be prioritized. Per one of the Mockito contributor's comments on the issue:

Given that .class does not play well with generics, I don't think there is any solution we can do in Mockito. You can already do @Mock (the JUnit5 extension also allows method parameter @Mocks) and that should be a suitable alternative. Therefore, we can keep this issue open, but it is unlikely ever to be fixed, given that @Mock is a better API.


For some cases spy() is alright, because you can pass an instance to it. Obviously doesn't cover all your bases but if you can instantiate a generic instance you're good to go.
v
vogella

With JUnit5 I think the best way is to @ExtendWith(MockitoExtension.class) with @Mock in the method parameter or the field.

The following example demonstrates that with Hamcrest matchers.

package com.vogella.junit5;                                                                    
                                                                                               
import static org.hamcrest.MatcherAssert.assertThat;                                           
import static org.hamcrest.Matchers.hasItem;                                                   
import static org.mockito.Mockito.verify;                                                      
                                                                                               
import java.util.Arrays;                                                                       
import java.util.List;                                                                         
                                                                                               
import org.junit.jupiter.api.Test;                                                             
import org.junit.jupiter.api.extension.ExtendWith;                                             
import org.mockito.ArgumentCaptor;                                                             
import org.mockito.Captor;                                                                     
import org.mockito.Mock;                                                                       
import org.mockito.junit.jupiter.MockitoExtension;                                             
                                                                                               
@ExtendWith(MockitoExtension.class)                                                            
public class MockitoArgumentCaptureTest {                                                      
                                                                                               
                                                                                               
    @Captor                                                                                    
    private ArgumentCaptor<List<String>> captor;                                               
                                                                                               
    @Test                                                                                      
    public final void shouldContainCertainListItem(@Mock List<String> mockedList) {            
        var asList = Arrays.asList("someElement_test", "someElement");                         
        mockedList.addAll(asList);                                                             
                                                                                               
        verify(mockedList).addAll(captor.capture());                                           
        List<String> capturedArgument = captor.getValue();                                     
        assertThat(capturedArgument, hasItem("someElement"));                                  
    }                                                                                          
}                                                                                              
                                                                                              

See https://www.vogella.com/tutorials/Mockito/article.html for the required Maven/Gradle dependencies.


q
qza

Here is an interesting case: method receieves generic collection and returns generic collection of same base type. For example:

Collection<? extends Assertion> map(Collection<? extends Assertion> assertions);

This method can be mocked with combination of Mockito anyCollectionOf matcher and the Answer.

when(mockedObject.map(anyCollectionOf(Assertion.class))).thenAnswer(
     new Answer<Collection<Assertion>>() {
         @Override
         public Collection<Assertion> answer(InvocationOnMock invocation) throws Throwable {
             return new ArrayList<Assertion>();
         }
     });

x
xilef

JUnit5: use @ExtendWith(MockitoExtension.class) on the test class then add this field:

@Mock
Foo<Bar> barMock;

This solution is already detailed in several other answers, I'm unsure how it adds any value.
@Pyves this covers JUnit5 which does not work with @RunWith(MockitoJUnitRunner.class)
I am seeing at least one other answer that already covered @ExtendWith(MockitoExtension.class), and other answers that work regardless of the version of JUnit in use. This isn't really the key point of the question/answer anyway.
范仲毅

why not using spy

var mock = spy(new Foo<Bar>());
when(mockFoo.getValue()).thenReturn(new Bar());

This will still lead to warnings,as highlighted by other answers.