On Wed, Jun 10, 2009 at 5:43 AM, Ed Sykes <ed.sykes@...> wrote:

> I've seen situations where the person on a team you would single out to
> infect produces a high level of quality of code without unit testing. In
> this case you have to show the leader that their team could produce more
> value if they were to adopt unit testing, even when the difference it makes
> for them is negligible.
>
> How would you do this?


A "high level of quality code" is great, yet most software lives on and on
and people expect to add/modify features in that software or debug it. How
much will the maintenance costs be without unit tests? How much more risk
does that add?

Most folks just look at today, not tomorrow. It's important to consider the
full cost of not writing unit tests.

HTH.

--
best regards,
jk

Industrial Logic, Inc.
Joshua Kerievsky
Founder, Extreme Programmer & Coach
http://industriallogic.com
866-540-8336 (toll free)
510-540-8336 (phone)
Berkeley, California

Learn Code Smells, Refactoring, TDD and Design Patterns at
http://industriallogic.com/elearning


[Non-text portions of this message have been removed]