On Sun, Oct 12, 2003 at 01:08:39PM +0000, Mark Stosberg wrote:
> I'm excited to see that the Phalanx project is happening.
>
> On the website I see this unfiled item:
>
> "Use Devel::Cover and gconv".
>
> One way that seems useful to use Devel::Cover is to have an automated coverage
> testing system that would test the 100 module periodically.
That would be useful.
> All the phalanx page, an extra column on the module page could like to the
> coverage results. This could be another way to track the test the progress.
>
> One sticking point I've noticed is that a different syntax is needed for
> modules that use Module::Build. That seems surmountable, though.
And it has already been surmounted. I sent a patch last week and Ken
Williams told me it has been applied in CVS and will be in the next
release, which will hopefully be before Hugo assimilates the module.
If you need it sooner:
--- Module/Build/Base.pm.org 2003-10-07 17:12:31.000000000 +0200
+++ Module/Build/Base.pm 2003-10-08 22:09:07.000000000 +0200
@@ -972,9 +972,9 @@
$self->depends_on('code');
# Do everything in our power to work with all versions of Test::Harness
- local ($Test::Harness::switches,
- $Test::Harness::Switches,
- $ENV{HARNESS_PERL_SWITCHES}) = ($p->{debugger} ? '-w -d' : '') x 3;
+ local ($Test::Harness::switches, $Test::Harness::Switches) = ('', '');
+ local $ENV{HARNESS_PERL_SWITCHES} = $ENV{HARNESS_PERL_SWITCHES} .
+ ($p->{debugger} ? ' -w -d' : '');
local ($Test::Harness::verbose,
$Test::Harness::Verbose,
> A second sticking point could be that code is OS-specific, so it's not ever going
> to get testing by just one build machine.
Correct, as is Tony's observation about different databases. Then
there's threads, filesystems, other modules which may or may not be
installed, external programs which may or may not be available, blah
blah blah, und so weiter und so fort etc. Fortunately, after running
Devel::Cover on these disparate systems, you can merge the databases to
collect the combined coverage.
It is also going to be a problem just getting these 100 modules
installed. I speak from some bitter experience, having spent some time
last week trying to do just that. An easily automated task it is not.
However, if you can install the modules and run the tests on appropriate
systems I think running Devel::Cover should be almost trivial in
comparison :-)
The current state of the art is http://pjcj.sytes.net/cpancover/ which
is just the modules I could (reasonably) easily install and test on my
system.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
