Just to be certain, I hope we are both talking about Devel-Cover-0.61 by
Paul Johnson.

Overall, the GUI for Coverage Analyzer is compelling, but it is very
lacking in the coverage tools it provides:

* perlcov-perl doesn't support Perl 5.6.1, whereas Devel-Cover does
* Devel::Cover creates a web based report, which is accessible to a
large development group
* The code displayed in Devel::Cover is colored, for easier reading
* There are several coverage tools in Devel::Cover not apparent in
Coverage Analyzer: conditionals, subroutine, pod
* The branch coverage tool in Coverage Analyzer is not obvious, it
should be part of the overall report
* I'd like to see a list of subroutines for each file and how much they
are covered
* I should like to export a report comparing results of different runs
* I'd like to specify which files to include in the coverage report,
especially if I am testing my project's modules

-David

-----Original Message-----
From: Jan Dubois [mailto:jand@[...].com] 
Sent: Tuesday, February 13, 2007 4:39 AM
To: Baird, David
Cc: pdk-beta@[...].com
Subject: Re: [PDK-Beta] Any feedback on PDK 7?

On Sun, 11 Feb 2007 12:00:42 +0200, "Baird, David" <dbaird@[...].com> 
wrote:

> On the Code Coverage, when I compare it to the CPAN Devel::Cover 
> module, I find the PDK application lacking. Have you looked at the 
> rather widely used CPAN module? I fail to understand why I should pay 
> for a feature I get for free and written better from CPAN.

Hi David,

Thank you for your feedback!

The new Code Coverage tool in PDK 7 is actually based on the
Devel::Cover module. It provides enhanced visualization for users, and
also provides management functionality for coverage data sets.  The
latter is not simply for convenience - it also allows for side-by-side
comparison of your code as it changes over time by changes to either
your modules or your test suite (for hotspot analysis and for code
coverage variation).

Some of this is presented in the sample data included with the Code
Coverage tool.  For coverage you can see the improvements of the test
suite in the Data-Dump sample code.  For hotspots the Ana-Find example
set shows the overall decreasing runtime over changes in the code.

We tried to provide users with a better visual overview of their code
based on the details Devel::Cover provides (without having to jump
through 100s of HTML pages). We were hoping to receive some feedback
from the beta users if they actually do find this representation more
useful, or if there are areas that could use additional GUI support.

To sum up, we believe the provided value is in the user interface that
provides the user with a better interface and subsequently better
understanding of their code, over time and/or at any point in time.
We have not as yet been able to finish a tutorial for the Code Coverage
tool, and we understand that makes it harder to grasp the features
provided.

We would be very interested in hearing more about why you find the Code
Coverage tool lacking in comparison to Devel::Cover.

Cheers,
-Jan

_______________________________________________
PDK-Beta@[...].com
http://listserv.ActiveState.com/mailman/listinfo/pdk-beta