Slash Boxes
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.
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 [] I've made previously and extract the modules used in each of the test files. They are just YAML files, so you pull out the right thing and count it.

      I extracted all the used modules using Module::Extract::Use [], which uses PPI to do the work. That way, I get everything the test file used.

    I'm finishing up the additions to MyCPAN::Indexer to spit this out, but I'm also thinking about only counting a Test:: module once per distribution.

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