Comments on: Quick Hits: Unit Testing iPhone Apps

By: Unit Testing on the iPad « Bloq Software

Unit Testing on the iPad « Bloq Software — Sun, 09 May 2010 04:11:06 +0000

[...] A “Kickass Labs” blog post about the subject (http://www.kickasslabs.com/2009/07/05/quick-hits-unit-testing-iphone-apps/) [...]

By: Rebecca

Rebecca — Mon, 03 Aug 2009 03:53:06 +0000

A couple things that have tripped me up:

1. In order to do app testing, you MUST build and run on the device; in order to do logic testing, you must build and run on the stimulator.

http://stackoverflow.com/questions/1092396/iphone-unit-testing-xcode

2. You can only test on devices running 3.0.

By: Brad

Brad — Tue, 07 Jul 2009 00:16:42 +0000

Marc – No, that’s a new one on me, but then I’m pretty new at this. I have noticed that things like linker failures can also trigger that error message – do you have any feedback from the build besides that one message?

By: Marc Chapman

Marc Chapman — Mon, 06 Jul 2009 20:42:54 +0000

You ever run into a situation where your general test fails, but the individual tests are all OK? I tried to add OCMock to my application, and I keep getting a general error:

error: Failed tests for architecture ‘i386′ (GC OFF)

By: Kickass Labs » Blog Archive » Quick Hits: Unit Testing iPhone Apps | Mac Affinity

Mon, 06 Jul 2009 09:13:27 +0000

[...] Excerpt from: Kickass Labs » Blog Archive » Quick Hits: Unit Testing iPhone Apps [...]

By: Brad

Brad — Mon, 06 Jul 2009 03:11:40 +0000

Chris – Thanks for the feedback.

I came to linking the object files directly because I got a linker error, and that was the thing I found that fixed it. I am, of course, always open to better ways of doing things.

At your suggestion, I’ve added the .m files for the classes under test to my unit tests target. It works well, and I don’t have to go hunting for the .o files. Thanks for the guidance. I’ll update the post accordingly.

By: Chris Hanson

Chris Hanson — Mon, 06 Jul 2009 02:27:19 +0000

Oh, one other thing: If you’re trying to link your test bundle against an application (via the Bundle Loader build setting), you’ll also have to tell your application target to export all of the application’s symbols.

Applications don’t default to exporting all of their symbols, unlike frameworks and static libraries.

By: Chris Hanson

Chris Hanson — Mon, 06 Jul 2009 02:25:09 +0000

You don’t “need to explicitly link the object files of the classes you’re testing.” It’s unclear how you got the idea that you do.

Either you need to add the sources for the classes you’re testing to your test bundle – making it what the unit testing docs call an “independent” test bundle – or you need to have your test bundle link against your application or library, making it a dependent test bundle.

Linking your test bundle against the object files directly shouldn’t ever be necessary.