I've been wanting to make a code coverage analysis tool for CF for a little while now. I don't know how possible it was before, but if there is a way to hook into the debugger I would think we can do it now.
If not, we'd likely have to build an entire cf engine. Or, I guess if we could write the unit testing frameworks in such a way that they inject harmless code into the code they are testing to track which branches get run ... and so forth. To my knowledge though, there isn't such a thing yet. On 10/29/07, Barry Beattie <[EMAIL PROTECTED]> wrote: > > > 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 -~----------~----~----~----~------~----~------~--~---
