OCMock with Core Data dynamic properties problem

Question

I\'m using OCMock to mock some Core Data objects. Previously, I had the properties implemented with Objective-C 1.0 style explicit accessors:

// -- Old Core          


        

Answer 1

Also responded to your cross-post on the OCMock Forum

Check out http://iamleeg.blogspot.com/2009/09/unit-testing-core-data-driven-apps.html.

Basically he suggests abstracting out your Core Data object's interface to a protocol, and using that protocol instead of the class where you pass instances of your core data object around.

I do this for my core data objects. Then you can use mockForProtocol:

id mockItem = [OCMockObject mockForProtocol:@protocol(MyItemInterface)];
[[[mockItem expect] andReturn:@"fakepath.pdf"] PDFName];

Works great! He also suggests creating a non-core data mock implementation of the interface which just synthesizes the properties:

@implementation MockMyItem
@synthesize PDFName;
@end

...

id  myItemStub = [[MockMyItem alloc] init] autorelease];
[myItem setPDFName:@"fakepath.pdf"];

I've used this as well, but I'm not sure it adds anything over the mockForProtocol:/stub: approach, and it's one more thing to maintain.