Jon Reid

I'm curious -- what does this add that can't be done by combining multiple `hasProperty` into an `allOf`?

Mockito features are slowly making their way to OCMockito. This one isn't there yet.

I'm sorry you've waited so long for an answer — I don't seem to be receiving any notifications from GitHub. For all mocked methods, `nil` is returned unless the `given`...

Thank you, @jasongrlicky. If you get a chance and are able to boil it down to an executable example, that would be really helpful.

Yes, this is about verifying that one call came before another.

@cerihughes I'd be interested in `stopAllMocks()`. But I'm also curious… what does your automatic solution look like? How does it work?

That's an interesting piece of information about OCMock! That helps nudge my opinion toward your last comment: "fix with documentation" rather than trying to avoid the problem in OCMockito.

Would you be willing to add a section to https://github.com/jonreid/OCMockito/wiki/OCMockito-FAQ ?

I would like to roll another release. @cerihughes how do you feel about `disableMocking`… - Still a keeper? - Unending edge cases, not worth it?

I'm interested in the idea of something that can register when mocks are created. Here's my main design goal: It should be optional. That is, existing tests should work fine...