Two days ago I uploaded the most recent version of my
module List::Compare to CPAN. This was the first
version in whose development I used Paul Johnson's
Devel::Cover to analyze the test suite's coverage of
the module's code and, as a result, over 3300 tests
were added, both to test new code and
On Tue, Aug 17, 2004 at 06:22:13AM -0700, Jim Keenan wrote:
Two days ago I uploaded the most recent version of my
module List::Compare to CPAN. This was the first
version in whose development I used Paul Johnson's
Devel::Cover to analyze the test suite's coverage of
the module's code and, as
The first thing I noticed after using Devel::Cover was how much output
it generates. The HTML files depicting the line-by-line status of the
coverage are enormous.
I assume you're talking about the large amount of data reported and not
the actual file sizes? The HTML files are massive
On Tue, Aug 17, 2004 at 04:21:09PM +, [EMAIL PROTECTED] wrote:
No. There's (currently) no option for doing so. The HTML is well formed,
though, which should make building a filter easy if you know how the
formatting works. ;) e.g.:
Or applying an XSLT file to it?
Tony
Tony Bowden [EMAIL PROTECTED] wrote:
On Tue, Aug 17, 2004 at 04:21:09PM +, [EMAIL PROTECTED] wrote:
The HTML is well formed, though, which should make building a filter
easy if you know how the formatting works. ;) e.g.:
Or applying an XSLT file to it?
The HTML reports are really
--- Paul Johnson [EMAIL PROTECTED] wrote:
By the way, how big is enormous? I had never
expected the size of the
HTML output to be a problem, but it obviously is to
some people.
'Enormous' is obviously a subjective judgment, so let
me describe the coverage files I've got and how I
worked
