I had a chance to use code coverage tools for Java in conjunction with unit testing - hadn't used them before and I was impressed with the concept.
it was especially good for seeing what code didn't run with the unit tests (showing holes in the tests themselves). I *could* sit there going line-by-line thru the new debugger or litter the code with logging traces - but seeing (easily) what code ran with the unit tests and what didn't was quite cool. I may be out of luck with the runtime nature of CF verses the compiling of Java code. but i'm still curious... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
