Unit Testing and Coverage in iOS Development with XcodeCoverage and OCMock

Tim Bray once said that the greatest contribution to software development in his lifetime will come from the rise of testing culture, not from any programming paradigm.

Unit testing is a white‑box testing technique that verifies a small, well‑defined piece of code (a function, method, or procedure) works as expected. Good unit tests follow the F.I.R.S.T principles: Fast, Independent, Repeatable, Self‑validating, and Timely.

Both front‑end and back‑end developers benefit from unit tests: they catch regressions when new features are added, help newcomers understand code, and give developers confidence when refactoring.

However, unit testing can increase development cost because Test‑Driven Development (TDD) requires writing tests before code, and measuring the effectiveness of tests is difficult without large‑scale controlled studies.

When Apollo first explored testing solutions, the team manually integrated XCodeCoverage and OCMock with Bamboo. Today the iBiu platform also supports XCodeCoverage, providing more convenient coverage generation.

Generating coverage with Xcode: 1) Add a unit‑test target to the project. 2) Enable code coverage for the target you want to test. 3) Adjust the target’s build settings. 4) Write test code and run Command+U to see coverage results. 5) Open the detailed report to see which lines are covered (green) or not (red).

Using XcodeCoverage: Install the library via a Podfile (or Podfile.custom when using iBiu) and run pod install. Also install two helper tools: gem install xcpretty and gem install ocunit2junit. Add a Run Script phase that executes ${PODS_ROOT}/XcodeCoverage/exportenv.sh.

After the script runs, an env.sh file is created. Edit OBJECT_FILE_DIR_normal and SRCROOT in this file so that XcodeCoverage scans the correct .gcno and .gcda files belonging to your business code rather than the example test target.

Run the coverage generator with ./getcov -s (show HTML), ./getcov -x (Cobertura XML), or ./getcov -o <output_dir> to export the report. The report lists total lines, covered lines, line‑coverage percentage, total methods, covered methods, and method‑coverage percentage, and lets you drill down to individual classes.

Common errors include missing .gcda files when external libraries are used. To ignore such libraries, create a .xcodecoverageignore file in the Classes folder and list the paths to be excluded.

Writing unit tests: Follow the Given‑When‑Then pattern, mock dependencies with OCMock, and assert results using XCTest’s XCTAssert family. Keep each test class focused on a single production class, and each test method on a single behavior.

When using OCMock, remember that mock objects are of type id, you can only have one mock per class, and you should call stopMocking after use. Use [OCMArg any] for arguments you don’t care about, but avoid it for primitive types.

In summary, unit testing and coverage analysis are essential for reliable iOS development; the combination of Xcode, XcodeCoverage, OCMock, and CI integration (Bamboo or iBiu) provides a complete workflow from writing tests to visualizing coverage.