In message <20050428203052.4537.qmail / web32207.mail.mud.yahoo.com>, 
Lorenzo Jorquera <lorenzo_jorquera / yahoo.com> writes
>>How will you know if it's the test or the code that's broken? Without
>>comments in the_func telling you why that exception is raised, you
>>could end up fixing the wrong problem.
>
>When you run your unit tests very often (tipically several times an 
>hour) you will know exactly why the test failed.

Wrong answer. You still are not documenting the "why".

Comments tell you what the code *SHOULD* be doing, not *WHAT* it is 
doing. So many people responding to this thread seem oblivious to this 
obvious, yet subtle and important fact.

Stephen
-- 
Stephen Kellett
Object Media Limited    http://www.objmedia.demon.co.uk
RSI Information:        http://www.objmedia.demon.co.uk/rsi.html