Re: Small extension for code coverage

Hi!

I am not doing deadcode analysis as it has a lot more implications than just hooking on execution and logging line hits; though I may include such functionnality via offline analysis in a futur tool that will transform fastcov's output into a nice HTML report.

This is the tricky part in coverage analysis :) The interesting data is how many lines are executed of those that might be (e.g., 100% coverage means all lines that could be executed were in fact executed). Of course, if you can't tell comments from live code, such file could never have 100% coverage. Doing it offline is fine, but having some way to do it IMHO is required for a good coverage system. BTW, you can look at what PHPUnit does fro HTML reporting, there are some nice features there.

As for the filename control, what parameters could be useful ? A format like xdebug ? Also I could probably add some metadata in the file itself.

I don't have particular ideas but maybe some ini setting and user-level function with formats, maybe like xdebug would be nice. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227