People often approach the code coverage thing by saying that you write more tests until you have some high percentage. There's another approach that says you delete application code until you have some high percentage. There's even a Java tool that will do this automatically, which is kind of extreme but interesting. If you rigorously follow TDD, in theory it will never delete anything useful, and the principle is that anything it does delete is untested and therefore dangerous.
Certainly my interest in code coverage analysis would be to identify unused execution branches, rather than flogging my team to write ever more post-facto tests. Jaime Metcher > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] Behalf > Of Barry Beattie > Sent: Wednesday, 31 October 2007 7:28 AM > To: [email protected] > Subject: [CFCDEV] Re: Code coverage tools for Unit Testing - do they > exist for CF? > > > > > It seems like this question comes up more and more often. > > that's because some ppl have seen it put to good use in the Java world > (inc me) and find the case for their use worthwhile, if not > compelling. > > the question I'd like to ask then is how do you know if you've written > enough unit tests? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
