Mockito provides mechanisms for mocking most of the stuff you need, but remains mysteriously silent on constructor mocking. “Newing up” an object when you are mocking in your unit tests is a pain, and I often found myself writing tiny factories to isolate where I was using a constructor.
For example, to test the following code…
1 2 3 4 5 6 7
You might end up writing something like this to make it more testable…
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Now you can inject a mock SomethingFactory in your test, and all the real SomethingFactory does is create your object with the appropriate arg and return it.
PowerMockito offers an enhancement to the Mockito API that let’s you sidestep this problem with its “whenNew” method, but their documentation is lacking.
To use, “whenNew”, you will need to supplement your typical Mockito test with a few enhancements.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
The important changes over a typical Mockito test are:
- The use of the PowerMockRunner in our JUnit @RunWith annotation
- The use of the @PrepareForTest method where we specify the name of the class we are testing (Helper.class in this case).
- The “throws Exception” on our method signature caused by the usage of “whenNew”
- The static invocation of the “whenNew” method, and our passing in the “argument” parameter”.
With these changes, you can roll back to the previous code, getting rid of your unnecessary factory and getting rid of some of the clutter from our Helper java class.