I haven't followed this thread that much but... My experiences are that the areas where unit testing help out are:
1) When the next guy wants to make a change it is easier for him/her to do it with confidence that they didn't break things. 2) It forces an implementer to think about the code in terms of external testablity which as a side effect I think leads to more flexible reusable code with less interdepenencies I believe the pain of not writing unit tests is really felt over the long term more than during the early phases of development. my 2 cents (because we didn't get enough opinions on this :-)) -----Original Message----- From: Leo Simons [mailto:[EMAIL PROTECTED] Sent: Mon 11/17/2003 9:20 AM To: [EMAIL PROTECTED] Cc: Subject: Re: shameless plug: articles on COP, other stuff Hamilton Verissimo de Oliveira (Engenharia - SPO) wrote: > I give up. don't take it too seriously, dude! Ulrich is dead wrong in considering unit testing a bad idea. You know that, I know that, but yet here @ avalon we, in practice, follow more of his methodology (little unit testing).....so he might actually have a point ;) cheers! - LSD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
