Comments on: Easier mocking with Mockito

By: Mihir

Mihir — Fri, 09 Jul 2010 13:41:25 +0000

How to write test cases for DAO layer in a Sruts applicaiton using Mockito?

By: Petri

Petri — Mon, 28 Jun 2010 18:31:32 +0000

I ended up here via Google, and I must say that this blog post is exactly what I have been looking for. I have been using Easymock for years in my projects, but recently I have been starting to investigate Mockito as its replacement. This is a very good explanation about their differences, and I am going to share this with my colleagues. Keep up the good work!

By: Rony

Rony — Mon, 21 Dec 2009 10:40:22 +0000

Very good post!

By: Julian

Julian — Wed, 02 Dec 2009 16:58:33 +0000

Here’s an interesting consequence of those default return values: null, 0 and false.

The equals() method on Mockito mock objects will return 0, so adding separate mock objects to a Set results in a just one of them in the Set, the others excluded because they’re all technically equal. Surprising if you expected the default identity equals of Object. Still, it’s an easy behaviour to explain and it’s consistent, and there are solutions to the equals problem, so a reasonable choice on balance.

I’ve previously used both EasyMock and JMock, and while I’m still in my first dozen classes developed with Mockito, it seems a solid alternative with some real benefits.

By: JTeam Technology Matrix: The Stars « JTeam Blog / JTeam: Enterprise Java, Open Source, software solutions, Amsterdam

Mon, 07 Sep 2009 10:30:17 +0000

[...] van Maris’ blog post titled Easier mocking with Mockito describes how to use Mockito and how it compares to [...]

By: Linkopedia August 2009 | From the Editor of Methods & Tools

Linkopedia August 2009 | From the Editor of Methods & Tools — Wed, 19 Aug 2009 05:36:27 +0000

[...] Easier mocking with Mockito [...]

By: Daily del.icio.us for August 13th through August 16th | Vinny Carpenter's blog

Sun, 16 Aug 2009 23:01:59 +0000

[...] Easier mocking with Mockito « JTeam Blog / JTeam: Enterprise Java, Open Source, software solut… – I hope you can see by now why Mockito is a better alternative to EasyMock. At JTeam we’re adopting Mockito in all our new projects. And whenever we have to go back to EasyMock, in the code from earlier projects, we know it was a good move. Happy mocking! [...]

By: Rob van Maris

Rob van Maris — Sun, 16 Aug 2009 09:55:30 +0000

Rogério, you're right. EasyMock does provide createNiceMock(...) to prevent overspecifying method calls, but this feature is relatively unknown. "Nice Mock" is not quite self-explanatory, and the documentation treats it as a highly advanced feature. As a result it is little used, and developers are discouraged to pay more attention to the risks of overspecification. Mockito, on the other hand, makes this "nice mock" the standard approach, much to its credit.

By: Richard Paul

Richard Paul — Sat, 15 Aug 2009 10:12:41 +0000

Good write up, I switched from EasyMock to Mockito a while ago and have never looked back. The main benefits are definitely test readability and avoiding over constraining of tests.

Mockito 1.8 also introduced BDD style aliases for those interested. e.g. given(…).willReturn(…) instead of when(…).thenReturn(…)
http://www.rapaul.com/2009/08/09/bddmockito-eclipse/

By: Jettro Coenradie

Jettro Coenradie — Sat, 15 Aug 2009 07:42:18 +0000

Very nice post, gives me more reasons to abandon easymock.

thanks