I wrote the following tools, and continue to use the Swift ones regularly. See which ones might help you.
A bad piece of code you can use for refactoring exercises, originally created by David Tanzer. Can you add tests, and clean up the code?
Learn Test-Driven Development by following the steps in this exercise, originally created by Robert Martin.
The Objective-C implementation of Hamcrest. It’s library of predefined matchers (which you can use in test assertions), and a framework for creating your own matchers.
The Objective-C implementation of Mockito. It supports creation, verification and stubbing of mock objects.
A “Paint by Numbers” TDD exercise originally created by Jeff Langr. We have provided the tests for you, all disabled. Your job is to do the rest: make the tests pass, then make your code clean. Sample solutions are provided.
Code snippets to help you write test cases. Available to all new subscribers.
Unit test alerts, presented view controllers, and dismissed view controllers.
A simple way to generate reports of the Objective-C code coverage of your Xcode project. Generated reports include HTML and Cobertura XML.
An xcconfig that enables lots of Xcode warnings.
Apple’s template fills test suites with cruft. By contrast, these test suite templates are sleek. They contain a single failing test, nothing else.