Tasty Test Tip: Using ArgumentCaptor for generic collections with Mockito - JDriven

Tasty Test Tip: Using ArgumentCaptor for generic collections with Mockito - JDriven

Tasty Test Tip: Using ArgumentCaptor for generic collections with Mockito Posted on For example: However, when using generic typed objects, some problems rise up. For example, the following won't work: ArgumentCaptor> argument = ArgumentCaptor.forClass(List.class); 1 ArgumentCaptor> argument = ArgumentCaptor.forClass(List.class); This is obviously not a Mockito problem, but a generics problem. To solve this, follow these two steps: 1. use the @Captor annotation. @Captor private ArgumentCaptor> argumentCaptor; 1 2     @Captor     private ArgumentCaptor> argumentCaptor; 2. initialize the Mockito annotations in your initialization method (add one if you don't have one). @Before public void init(){ MockitoAnnotations.initMocks(this); } 1 2 3 4     @Before     } And presto! You can now capture the parameters that were used when a to be verified method was executed. verify(someMock).

Read full article from Tasty Test Tip: Using ArgumentCaptor for generic collections with Mockito - JDriven