ObjectiveC-UnitTesting&MockingObjects?

11  

Inversion of control is still feasible in objective-c. You can certainly design your classes with constructor-based or property-based dependency injection in mind but I don't think you'll find an annotation based dependency injection framework like you are used to.

在目标c中，控制反转仍然是可行的。您当然可以设计基于构造函数或基于属性的依赖注入的类，但我认为您不会像以前那样找到基于注释的依赖注入框架。

[[ClassToBeTested alloc] initWithDependency:foo andOtherDepedency:bar];

ClassToBeTested *objectUnderTest = [[ClassToBeTested alloc] init];
objectUnderTest.dependency = foo;
objectUnderTest.otherDependency = bar;

I've seen a couple of different approaches to building dependency injection frameworks for objective-c including https://github.com/mivasi/Objective-IOC but I can't comment on their maturity or usefulness.

我已经看到了为objective-c构建依赖注入框架的几种不同方法，包括https://github.com/mivasi/Objective-IOC，但我无法评论它们的成熟度或实用性。

For object mocking and stubbing look at OCMock.

对于对象模拟和存根，请查看OCMock。

7  

how can you mock MyObject?

你怎么能模仿MyObject？

- (void) methodToBeTestedWithObject:(MyObject *)object
{
     NSString str = @"myString";
     [object setString:str];
     [object doStuff];
}

To test:

去测试：

- (void)testMethodToBeTested {
    id mockMyObject = [OCMock mockForClass:[MyObject class]];

    [[mockMyObject expect] setString:[OCMock any]];
    [[mockMyObject expect] doStuff];

    [objectToTest methodToBeTestedWithObject:mockMyObject];
    [mockMyObject verify];
}

Using, as mentioned in @Jonah's answer, the excellent OCMock. Don't bother trying to do capital-D, capital-I Dependency Injection in obj-c, it's more work than it's worth.

正如@Jonah的回答中所提到的，使用优秀的OCMock。不要费心去做资本-D，资本-I Dependency Injection in obj-c，它的工作量超过了它的价值。

1  

Here's a dependency injection framework for Objective-C: http://www.typhoonframework.org

这是Objective-C的依赖注入框架：http：//www.typhoonframework.org

Besides addressing on the design aspects of DI, it has a strong focus on being able to configure components for production vs test scenarios (integration testing). This includes:

除了解决DI的设计方面外，它还非常注重能够为生产与测试场景（集成测试）配置组件。这包括：

• Ability to inject values represented as strings - these are converted to the required type at runtime.
• 能够注入表示为字符串的值 - 这些值在运行时转换为所需的类型。
• Configuration management via an external properties file.
• 通过外部属性文件进行配置管理。
• Asynchronous test execution - allowing you to test methods that run on a background thread.
• 异步测试执行 - 允许您测试在后台线程上运行的方法。