Hi Szczepan,

I would expect the following test to pass. What are your thoughts?

Cheers, felix

public class MockitoVarargTest {

interface VarargMethod{
  Object run(String... args);
}
@Test
public void testVarargStubbing(){
    Object returnValue = new Object();
    VarargMethod mock = Mockito.mock(VarargMethod.class);
    when(mock.run((String[]) anyObject())).thenReturn(returnValue);
    assertEquals(returnValue, mock.run("a", "b"));
}

}

I'll look at it

I think we discussed this issue with patric back at gu, but unfortunately I can't remember, what came out of that...

It makes sense the anyObject() should match any number of elements in the varArg array.

It's fixed in trunk. Thanks Felix for reporting!

Reopened as the fix for this bug introduced regression. This is how you reproduce it:

    //when
    table.newRow("qux", "foo", "bar", "baz");
    table.newRow("abc", "def");

    //then
    verify(table).newRow(anyString(), eq("foo"), anyString(), anyString());
    verify(table).newRow(anyString(), anyString());

Reverted the fix for this issue as it makes other part of verification broken for some corner cases.

Fix for this issue will go to further milestone.

I officially don't have time for this feature :)

If anyone is keen on this feature, please submit a patch.

This cannot be implemented as it would change the behavior of other parts of the framework. Namely, it affects counting of actual invocations vs verified invocations.

Instead, I introduced new matcher: anyVararg()

That's great! Any release plans yet?

I'm working on it - should be couple of days :)