ArgumentMatcher like assertArg() for multiple different calls?

[jpgoelz]

When verifying multiple different calls to a method of a mock, it is possible to call verify() twice for each invocation.

This will work when not using matchers:

    @Test
    @DisplayName("verify two different calls")
    void verifyTwoDifferentCalls() {
        someMock.someMethod(1, "any string");
        someMock.someMethod(2, "any string");

        verify(someMock).someMethod(1, "any string");
        verify(someMock).someMethod(2, "any string");
    }

This will also work when using simple matchers:

    @Test
    @DisplayName("verify two different calls with eq()")
    void verifyTwoDifferentCallsWithEq() {
        someMock.someMethod(1, "any string");
        someMock.someMethod(2, "any string");

        verify(someMock).someMethod(eq(1), anyString());
        verify(someMock).someMethod(eq(2), anyString());
    }

However, it does not work when using assertArg():

    @Test
    @DisplayName("verify two different calls with asserArg()")
    void verifyTwoDifferentCallsWithAsserArg() {
        someMock.someMethod(1, "any string");
        someMock.someMethod(2, "any string");

        verify(someMock).someMethod(
            assertArg(someInt -> assertThat(someInt).isEqualTo(1)),
            anyString()
        );
        verify(someMock).someMethod(
            assertArg(someInt -> assertThat(someInt).isEqualTo(2)),
            anyString()
        );
    }

The reason behind this is probably the inner assertion failing on at least one of the calls.

So far, the only way I know how to test something like this is to use ArgumentCaptors:

    @Test
    @DisplayName("verify two different calls with ArgumentCaptor")
    void verifyTwoDifferentCallsWithArgumentCaptor() {
        someMock.someMethod(1, "any string");
        someMock.someMethod(2, "any string");

        final ArgumentCaptor<Integer> someIntCaptor = ArgumentCaptor.forClass(Integer.class);

        verify(someMock, times(2)).someMethod(someIntCaptor.capture(), anyString());

        assertThat(someIntCaptor.getAllValues()).containsExactly(1, 2);
    }

Now, my question: Is there any way to do this without using an ArgumentCaptor?

[jpgoelz]

Btw: I also tried inOrder without success:

    @Test
    @DisplayName("verify two different calls with asserArg() and inOrder()")
    void verifyTwoDifferentCallsWithAsserArgAndInOrder() {
        someMock.someMethod(1, "any string");
        someMock.someMethod(2, "any string");

        final InOrder inOrder = inOrder(someMock);

        inOrder.verify(someMock).someMethod(
            assertArg(someInt -> assertThat(someInt).isEqualTo(1)),
            anyString()
        );
        inOrder.verify(someMock).someMethod(
            assertArg(someInt -> assertThat(someInt).isEqualTo(2)),
            anyString()
        );
    }

[abendt]

Just ran into the same issue, then found this Q&A. Is there already a bug/feature request for it?

[jpgoelz]

I guess you should just use an ArgumentCaptor.