Comments on: Unit Testing.

By: bluelobe

bluelobe — Wed, 10 Aug 2011 05:52:21 +0000

If one is an expert in SQL and has years of experience doing SQL and has mastered SQLite in iOS, would you recommend they still move to CoreData? When I say expert, I mean, all their apps are full-featured db-wise and only use SQLite and do so quickly, bug-free, and development time is super-fast and super-efficient.

By: References on Unit Testing & UI Automation for iOS Applications | Jojit Soriano's Blog

Fri, 03 Jun 2011 02:03:01 +0000

[...] testing is difficult for application development – Unit Testing is teh suck, Urr. by Wil Shipley + Unit Testing. by bbum – How to Write Your Own Automated Testing Framework by Gus [...]

By: Gin margarita via unit testing UIs – Ross Henderson

Gin margarita via unit testing UIs – Ross Henderson — Thu, 15 Jul 2010 19:38:51 +0000

[...] found it by luck, reading this post, about unit testing, which was a response to this post about testing [...]

By: Lukasz Wrobel

Lukasz Wrobel — Wed, 10 Feb 2010 21:15:20 +0000

While I regard writing unit tests to be controversial, I decided to write out a few most commonly encountered opinions and talk them over: Unit Tests – Love, Ignorance and Getting Real

Perhaps you will become interested in this article, especially if you have a strong (either positive or negative) opinion on applying unit tests.

By: Unit Testing: Good/Bad?

Unit Testing: Good/Bad? — Tue, 25 Aug 2009 19:44:34 +0000

[...] Bumgarner counters with a good argument of when this case occurs and how unit testing can solve a [...]

[Ed:] Unfortunately, the mojomonkeycoding.com weblog’s comment system is busted. The author of that post missed the point. If he had been paying attention, he would realize that unit testing is critical in a well designed app in that you will have a model/control layer that is a great UT target.

By: Red Sweater Blog - Unit Testing Roadblocks

Red Sweater Blog - Unit Testing Roadblocks — Fri, 01 Aug 2008 22:43:20 +0000

[...] existing code base. I won’t go into much more about the whens and ifs, but Wil Shipley and Bill Bumgarner have delved deeper into this question, if you’re interested in reading [...]

By: Sander’s Weblog » Unit Testing Not Necessarily teh suck

Sander’s Weblog » Unit Testing Not Necessarily teh suck — Mon, 31 Dec 2007 00:09:55 +0000

[...] course exaggerating for effect and the post is best taken in together with BBum’s excellent follow-up where he argues that unit testing made a huge amount of sense for his project, but may be less [...]

By: Christopher Humphries

Christopher Humphries — Wed, 15 Aug 2007 22:49:12 +0000

Wow, thanks. Very good post (got from linked off Wil’s blog post on unit testing).
Bookmarking

By: Dan Waltin

Dan Waltin — Tue, 03 Jul 2007 21:46:37 +0000

This is a late comment, I just found this entry (which has many good points)! Now, in response to Bill Dudney “How do you debug your tests?”: Given that the (unit) tests are supposed to reveal bugs in your code, one approach I will test in my current project is to appoint a “saboteur”. This is a person that takes a branch of the code an insert bugs to see if the tests find them!

Insert a “throw new ApplicationException(“This has not happened”) (*) here and remove an input validation there…

This is not automatic, I know, but I guess that a good sabouteur can make a difference. Anyone tried this technique?

/Dan

(*) Unfortnunately I’m not able to program Objective-C for a living, but C# is really quite nice…

By: The End of the Long Tail » To Unit Test or Not to Unit Test? That is the Question.

Sun, 11 Mar 2007 14:36:22 +0000

[...] I said, “rarely a good practice”. Here an Apple developer explains when unit testing is not a waste. Appreciate the differences in [...]