OCMExpect() broken for OCMockObject::notificationWithName:object:userInfo:

[markeissler]

In short, this doesn't work (returns "unrecognized selector sent to instance"):

OCMExpect([mockObserver notificationWithName:@"MyNotification" object:[OCMArg any] userInfo:[OCMArg any]]);

But this (the old syntax) does...

[[mockObserver expect] notificationWithName:@"MyNotification" object:[OCMArg any] userInfo:[OCMArg any]];

Omitting the userInfo: parameter in the first example works provided that the notification sends nil for userInfo.

[erikdoe]

Observer mocks are not supported by the (now not so) new syntax with macros. The documentation deliberately shows only the selector-based syntax: http://ocmock.org/reference/#observer-mocks

I'll leave this issue open as a reminder that I should add something for observer mocks to make them work with the new syntax.

The underlying issue is that the macro always creates a recorder for normal methods (

ocmock/Source/OCMock/OCMMacroState.m

Line 47 in e50f4f9

OCMExpectationRecorder *recorder = [[[OCMExpectationRecorder alloc] init] autorelease];

) but the expect method on the observer mock returns a special notification recorder (

ocmock/Source/OCMock/OCObserverMockObject.m

Lines 72 to 74 in e50f4f9

	OCMObserverRecorder *recorder = [[[OCMObserverRecorder alloc] init] autorelease];
	[recorders addObject:recorder];
	return recorder;

).

When I got to the release of OCMock 3, I couldn't think of a good way to resolve this, short of merging the observer recorder functionality into the other recorder, which I didn't like. Any ideas?

[erikdoe]

This was implemented a long time ago. Forgot to close this issue.