One Unit Test Framework to Rule Them All

I kid myself about changing my mind daily regarding the “best” unit testing frameworks. I’ve been advocating for Kiwi for several months now. Well, here goes again.


Pros: I absolutely love Kiwi. It allows test to be well organized (RSpec style), has excellent mock support (including Class mocks), is fast, and is easy to use (runs on top of OCUnit logic tests), and has asynchronous support.

Cons: Debugging tests is difficult. Whenever I try to debug tests, I typically get dumped into assembler code. Yech!

Maybe I just don’t understand how to debug block code.

I’ve also been considering whether having disorganized tests is actually a symptom (smell) of having classes that are too big. I’ve been reviewing an associate’s code that uses OCHamcrest and Mockito, and I must say that I find it quite readable.

So, the current HowsMyFuel TDD project (April 22, commit 068c19d75e) fails unit tests, and it isn’t clear why. I could probably guess, and use trial-and-error to fix it, but I’d prefer to have a clear diagnostic approach to debugging and fixing tests.

So I’m going to rewrite the tests using OCUnit, OCHamcrest, and OCMockito and see if the error occurs, and if so, how tough it is to debug and fix.

3 thoughts on “One Unit Test Framework to Rule Them All

  1. Have you considered Specta, Expecta and OCMockito? Then at least you’re not giving up spec-based. I settled with these three after surveying those available. Maybe someday there will be a “Mockta” 🙂

  2. I haven’t had any trouble stepping through code with Kiwi 2.2.1 in Xcode 4.6.x. I’ve never seen the dumping into assembler code problem. Maybe they’ve ironed out that bug in the latest version.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.