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*.
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
