Re: Clover Fight! :-)

Jason,

>As noted by Paul it is much easier for others to be involved if you're
>well covered and that only makes sense. But I think in our particular
>case if our containers are covered I think we could more easily explore
>each others code and might eventually help toward a merger of more bits
>and pieces in the future.
>  
>
The other benefit is that commits that break security models and deviate 
from planned design are harder to squeeze in if the unit tests prove 
your maxims. For example implementation hiding is easily provable via a 
unit test.  PeterD could go on a months holiday and no committer could 
break that in Loom without commenting out the pertinent test case.  
Historically relevant to many of us.

Sometimes in full blown containers or fat client/server stuff, it is 
better to aim at integration tests to prove things.  Also we must 
remember to not modularise out unit tests too much - they are snippets 
of example code.

I shudder to think of the amount of legacy code I have to be precious 
about, that I coded in my pre TDD days.  If only...

- Paul


-- 
http://www.thoughtworks.com -> The art of heavy lifting.
Home for many Agile practicing, Open Source activists...