Comments on: Improve your unit-tests with jMock2

By: Alan van Dam

Alan van Dam — Fri, 05 Sep 2008 07:50:05 +0000

@Gene, Yes the @RunWith could be a problem if your are already using one. Adding a call ‘mockContext.assertIsSatisfied();’ at the end of your test will also check the expectations. But this could easily be forgotten. Maybe time for some more comparison between the two. I found a nice comparison: http://jeantessier.com/SoftwareEngineering/Mocking.html

By: raveman

raveman — Thu, 04 Sep 2008 15:16:21 +0000

I started with JMock and then i moved to EasyMock and never look back, the way i see it its just API. Both have almost the same feauters – with JMock2 you use anonymous inter classes with EasyMock static imports. @RunWith may make EasyMock better.

By: Gene De Lisa

Gene De Lisa — Thu, 04 Sep 2008 11:47:31 +0000

@RunWith(JMock.class) is a problem.

How can you use jmock mocks with this:
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration

My answer: EasyMock. Unless you have another way?