Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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.
    • 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 [grango.org] 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.

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