views:

635

answers:

2

Hi,

I have a method i'd like to stub but it has a lot of parameters. How can i avoid mocking all parameters but still stub the method.

Ex:

//Method to stub
public void myMethod(Bar bar, Foo foo, FooBar fooBar, BarFoo barFoo, .....endless list of parameters..);
+1  A: 

Create a wrapper class which calls the real method and fills in all the arguments but the ones you supply (a.k.a "delegation").

And at the next opportunity, file a bug against the project asking to move the parameters to a config object.

Aaron Digulla
True - too many parameters on a method signature is a bad code 'smell'.
hbunny
I'm having 5 parameters, and yes they are needed:) It's a service method i'm trying to stub. I only wanted to be theoretical for methods where you don't really want to stub the parameters
Michael Bavin
+3  A: 

I don't quite follow what problem you're having using Mockito. Assuming you create a mock of the interface that contains your myMethod() method, you can then verify only the parameters to the method that you are interested in. For example (assuming the interface is called MyInterface and using JUnit 4):

@Test
public void test() {
    MyInterface myInterface = mock(MyInterface.class);
    FooBar expectedFooBar = new FooBar();        

    // other testing stuff

    verify(myInterface).myMethod(any(), any(), eq(expectedFooBar), any(), ...);
}

You'll need to do a static import on the Mockito methods for this to work. The any() matcher doesn't care what value has been passed when verifying.

You can't avoid passing something for every argument in your method (even if it's only NULL).

hbunny
I guess he really wants to call myMethod(), so he needs to pass all those parameters every time which bloats the test.
Aaron Digulla
I'm testing a controller and i'm stubbing my service method. the service is mocked. I guess the any() should work. Thanks
Michael Bavin