On Fri, Sep 21, 2007 at 05:51:36AM -0400, James E Keenan wrote: > Michael Carman wrote: > >On 9/12/2007 7:41 PM, James E Keenan wrote: > >>I'd also like to hear any other coverage-related ideas you think would > >>be worthwhile bringing up at this workshop. > > > >Here's my 2ยข > > > >For applications with code in multiple modules use the options for > >including and > >excluding files (-ignore, +inc, -select, etc.) to ensure that you're only > >collective coverage for the thing that's being actively tested. You're > >limited > >to file-level granularity but it's still a big improvement over collecting > >lots > >of incidental coverage. > > > > The options you mention are for 'cover', the utility which generates > reports from the database generated when you run tests with > -MDevel::Cover or its equivalent. AFAICT, the options you select have > no impact on the amount of data you *collect*, only on the amount you > *report*.
Actually, the options Michael gave *are* for Devel::Cover itself. There are similar (but slightly different - and I hate that) options for cover. And you are quite right about the options to cover only affecting the reporting, which is why it is very helpful to be able to give these options to Devel::Cover, where they can reduce the amount of data collected, and thus increase the speed at which it is collected. > I will be covering some of these coverage reporting options at PPW. If > you have actual use cases, please post. Thank you very much. > > Jim Keenan > -- Paul Johnson - [EMAIL PROTECTED] http://www.pjcj.net
