Comments on: An interesting blog post about Mockito (and other mocking frameworks) http://dahliabock.wordpress.com/2009/04/21/an-interesting-blog-post-about-mockito-and-other-mocking-frameworks/ Thu, 26 Nov 2009 18:42:14 +0000 http://wordpress.com/ hourly 1 By: Mocking: Mockito vs EasyMock example « Dahlia Bock http://dahliabock.wordpress.com/2009/04/21/an-interesting-blog-post-about-mockito-and-other-mocking-frameworks/#comment-144 Mocking: Mockito vs EasyMock example « Dahlia Bock Mon, 24 Aug 2009 04:05:51 +0000 http://dahliabock.wordpress.com/?p=225#comment-144 [...] since I was introduced to Mockito about a year ago, I’ve been a big fan. I wrote a couple of posts about it and promised a long, long time ago that I would post an example of a test written in [...] [...] since I was introduced to Mockito about a year ago, I’ve been a big fan. I wrote a couple of posts about it and promised a long, long time ago that I would post an example of a test written in [...]

]]> By: Dahlia Bock http://dahliabock.wordpress.com/2009/04/21/an-interesting-blog-post-about-mockito-and-other-mocking-frameworks/#comment-88 Dahlia Bock Tue, 21 Apr 2009 10:12:54 +0000 http://dahliabock.wordpress.com/?p=225#comment-88 I appreciate your opinion and I don't mean to be rude but I would like to hear from other people given that you were the one who wrote the blog post :) I appreciate your opinion and I don’t mean to be rude but I would like to hear from other people given that you were the one who wrote the blog post :)

]]> By: rrees http://dahliabock.wordpress.com/2009/04/21/an-interesting-blog-post-about-mockito-and-other-mocking-frameworks/#comment-87 rrees Tue, 21 Apr 2009 09:58:49 +0000 http://dahliabock.wordpress.com/?p=225#comment-87 I would characterise my opinion as being that Mockito does not necessarily "encourage" developers to be lazy but that it's ease of use carries with greater <i>risk</i> of the issues you mention happening. I also strongly disagree that there is an issue of JMock "noise", there is the <i>Java</i> noise around anonymous inner classes and my concern is that it is not noise that gets erased but the intent of the code. I would characterise my opinion as being that Mockito does not necessarily “encourage” developers to be lazy but that it’s ease of use carries with greater risk of the issues you mention happening.

I also strongly disagree that there is an issue of JMock “noise”, there is the Java noise around anonymous inner classes and my concern is that it is not noise that gets erased but the intent of the code.

]]>