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.
  • On the plane today I made this a feature of my BackPAN indexer. I have all the bits to take a list of distributions and look inside them, so I just needed a worker task to count test modules instead of doing all the other stuff. It mostly works now, and I've pushed it to github. It's not like you need to care about that because I'll do the work to make the reports. :)

    If you really wanted to, you could also look through the output files [perl.org] I've made previously and extract the modules used in each of the test fi

    • Thanks for doing this. That's great!

      The other day, Schwern mentioned on the Test::More development list the other day that CPANTs also does the "once per distribution" thing. Counting the test module once per distribution as opposed to once per test program is good, but offers a different use case. It shows how widespread the dependency is, but not how widespread the usage is (both numbers being valuable, of course).

      For example, if you have one distribution with five .t programs, if one uses Test::Pod and the other four use Test::More, it's clear that Test::More is used more frequently, but also clear that this distribution depends on Test::More once, not four times :)

      So whichever way you count, it just depends upon which problem you want to solve.