All the Perl that's Practical to Extract and Report

CPAN Module Smoking

BinGOs on 2006-11-18T15:35:27

So if anyone has been following my previous adventures with CPAN testing and my efforts to create a POE-based framework, I have started componentising my wildly successful bunch of hacked up scripts.

Part one has been released to CPAN and goes by the name of POE::Component::CPAN::YACSmoke.

I'll be following this up with a number of revised scripts in the next few weeks.

Automation of module testing

scot on 2006-11-20T16:30:06

Glad to hear that you are releasing this! Automating the module testing process as you have done should be recognized as a heroic achievement. I am a firm believer that anything that can be automated should be automated. Your work will result in a huge productivity gain for Perl developers. Anyone who takes a look at the cpan-testers mailing list will see that you've been generating 90% or thereabouts of the test results.

Re:Automation of module testing

barbie on 2006-11-20T19:12:11

you've been generating 90% or thereabouts of the test results.

Only just recently. Chris still has a long way to go before he over takes Jost in the big money stakes ;)

Once I get through the upgrade of the test suite for yacsmoke, I'll include Chris' module in the documentation and possibly a howto as well.

Re:Automation of module testing

BinGOs on 2006-11-21T08:30:33

I'm looking forward to the new shiny CPAN::YACSmoke

I see from looking in SVN that it now uses CPANPLUS' _home_dir() method to work out where to store it's files, which should make it way easier to have multiple test perl installations in one home directory and fudge APPDATA environment to use different .cpanplus/ folders.