Comments on: Unit Testing for Developers and Managers

By: Be Prepared To Be Surprised | The Freak Parade

Be Prepared To Be Surprised | The Freak Parade — Sat, 11 Oct 2008 08:28:39 +0000

[...] as Udi Dahan points out, we often feel we are not at liberty to go off experimenting with change at the expense [...]

By: Learning On A Project - Ian Cooper [MVP]

Learning On A Project - Ian Cooper [MVP] — Fri, 10 Oct 2008 08:30:58 +0000

[...] original post about increasing TDD adoption. Roy updates some of the reaction here and here. Udi comments on my reaction that the most important thing is to being writing tests and then learn how to write [...]

By: Alan

Alan — Wed, 01 Oct 2008 20:54:59 +0000

Excellent post, I will go “broadcast” in my blog.
Some managers sacriface yours project only by cost and pmi pratices, but to test domain model is very important. Managers should not to do this.

By: jdn

jdn — Wed, 01 Oct 2008 15:43:27 +0000

Alleluia.

By: udidahan

udidahan — Wed, 01 Oct 2008 15:05:44 +0000

Casey,

I think that that’s about right.

By: Testing Is Not Technically Hard, It Is Hard Because It Requires Clear Thought and Understanding - Casey Charlton - Insane World

Wed, 01 Oct 2008 09:09:14 +0000

[...] Unit tests are not technically hard, as Udi points out, what is a test? Anything with TestFixture on it? [...]

By: Casey

Casey — Wed, 01 Oct 2008 06:43:27 +0000

An excellent post. I think, and hope, what you are saying is any code that does not add *business* value is of low value, and tests that have no clear purpose, or that further concrete an already weak design, will ultimately decrease business value.

Saying “we have tests” is relatively worthless, saying we have our core logic fully tested and can now refactor or evolve safely has immense value.

By: Robin Clowers

Robin Clowers — Tue, 30 Sep 2008 22:14:37 +0000

Great post Udi, I have been thinking a lot lately about the value of unit tests in certain parts of a system, and I think you hit the nail on the head.