Comments on: Unit Testing.

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 [...]

By: Don Lapre Lover

Don Lapre Lover — Mon, 27 Nov 2006 23:36:23 +0000

The post was interesting to read. I have always been a fan of the automated test but there is something to be said about one on one.

Laura
Don Lapre Lover
http://www.lauraglydaband.com
laura@lauraglydaband.com

By: Bill Dudney

Bill Dudney — Wed, 01 Nov 2006 12:22:59 +0000

Hi,
How do you debug your tests? I’ve googled around quite a bit for an answer and its not jumping out of the web at me. Hoping you know…

Thanks

By: Scott’s Blog » Why Unit Test

Scott’s Blog » Why Unit Test — Tue, 29 Aug 2006 16:08:49 +0000

[...] I came across a great post on unit testing today that provided not just why to unit test, but what to unit test. Differentiating software into “infrastructure” and “end user application” really highlights what sort of code will benefit the most from the approach. Another really useful bit of this article talks about turning bug reports into unit tests. It’s a very smart idea that I’ll try to use on my own code whenever it’s appropriate. You can also bookmark this on del.icio.us or check the cosmos [...]

By: Oscar Morales Vivo

Oscar Morales Vivo — Wed, 05 Jul 2006 21:07:51 +0000

Ah, great to find someone who had put in words what I was thinking about. In the end, testing infrastructure tends to be far less problematic than doing it to GUI programs since the inputs are much better controlled and easier to code into being. For actually breaking a shipping application, however, there’s nothing like users :P.

Now the hard part will be to convince the other devs in my team to actually use unit testing (for those parts of our work where it makes sense to do so). They still have occasionally a problem with the whole ‘comment your code’ thing so I’m not too optimistic about it :P.

By: Houman

Houman — Mon, 22 May 2006 23:02:20 +0000

Well Put.

By: Rob Rix

Rob Rix — Tue, 20 Dec 2005 08:28:33 +0000

Just wanted to note, my -copyWithZone: implementation for NSManagedObject is now on a different site. I’ve had a couple of people e-mail me so I figured I’d let anyone know. Sorry about the post!