Using partialMockForObject to do singleton class mock, how to create a method like "removeAllExpectations” to remove all remembered ones?

2
votes

Confused on OCMock for singleton, get two methods, but none of them is perfect in my opinion.

  1. Using partialMockForObject. I want to use partialMockForObject to do singleton class mock. See following code, it works well, but the defect is that singleton [NSNotificationCenter defaultCenter] will remember previous mock behavior, then when invoked in another place, it will crash, unexpected. So my question is that how can I create a method like "removeAllExpectations” to remove all remembered ones?

    id aMock = [OCMockObject partialMockForObject:[NSNotificationCenter defaultCenter]];

    [aMock expect] removeObserver:[OCMConstraint isKindOfClass:[WhereIsMyPhoneViewController class]]];

    [[aMock verify];

  2. Using category method. See http://twobitlabs.com/2011/02/mocking-singletons-with-ocmock/ mentions another method to do singleton mock, personally I prefer partialMockForObject, you don't need to mock all methods when unit testing.

Have sent my question to OCMock development group but no response got yet, need your smart guys opinion. Any idea or discussion will be appreciated, thanks in advance.

2
singletonocmock
I wish this question was actually answered, as this is exactly what I'd like to do in my test. Have 1 logical test instead of splitting up into 3+ tiny tests, and reset in-between. – SilverSideDown

2 Answers

4
votes

If you are using the lastest source code of OCMock (after 2012-04-06), call

[aMock stopMocking];

to reset the mocked object's state.

1
votes

You can call:

[aMock stop];

to reset the mocked object's state.