Comments on: Fun with jMock http://blog.palantirtech.com/2009/11/22/fun-with-jmock/ Articles from the Engineering Group at Palantir Technologies Tue, 24 Jan 2012 09:51:18 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Steve Freeman http://blog.palantirtech.com/2009/11/22/fun-with-jmock/comment-page-1/#comment-267 Steve Freeman Tue, 24 Nov 2009 11:20:14 +0000 http://blog.palantirtech.com/?p=1274#comment-267 Thanks for the reference. There are a few extra points to note: Adding @RunWith(JMock.class) to the JUnit class will call assertIsSatisfied() automatically for each test When we specify a query, such as: oneOf(service).getObject(realm.getId(), myObject.getId()); will(returnValue(myObject)); we usually make that allowing(service).getObject(realmId, objectId); will(returnValue(myObject)); Queries don't change the world outside the object, so we stub them to express that relationships and to make the tests more resilient as the code changes. Thanks for the reference. There are a few extra points to note:

Adding @RunWith(JMock.class) to the JUnit class will call assertIsSatisfied() automatically for each test

When we specify a query, such as:

oneOf(service).getObject(realm.getId(), myObject.getId()); will(returnValue(myObject));

we usually make that

allowing(service).getObject(realmId, objectId); will(returnValue(myObject));

Queries don’t change the world outside the object, so we stub them to express that relationships and to make the tests more resilient as the code changes.

]]>