Verifying that class factory method calls the corresponding `init` method about ocmockito HOT 3 CLOSED

So after a short investigation I found that I understood the whole concept of mocking in a bad way. The behavior I thought to be invalid is indeed valid - mock object doesn't forward messages to an underlying instance, it's a job for partial mocks, that are not yet implemented, right?

from ocmockito.

Correct, partial mocks aren't implemented yet. But beware, partial mocking can be a code smell. In your case, what you're trying to specify seems too restrictive. Try to think in terms of observable effects, and you may find there's no need for a mock at all. For example:

- (void)testLessonShouldHaveGivenName
{
    // given
    LessonModel *lesson = [LessonModel lessonWithName:@"NAME"];

    // then
    assertThat([lesson name], is(@"NAME"));
}

In other words, don't write a test that one method calls another within its own class. That only leads to fragile, overspecified tests that keep code from being flexible. Instead, call the method and test that it does the right thing. Use mocks only for things that are too expensive or unreliable (like database or network access) or for systems you don't own (like Cocoa singletons).

from ocmockito.

Thank you!

from ocmockito.