Hi, I'm an ever-increasing fan of CPAN testers, and a more recent convert to the value of dev releases. I installed CPAN::Reporter, so I can "do my bit".
One thing I've noticed is that when I do a dev release, the next day I have a lot fewer test results than for a regular release. Which isn't very surprising, since I generally don't install dev releases, but do install a lot of regular releases, and assume that's true of quite a few manual users of CPAN::Reporter. I was wondering if there's a way to just do test builds of dev releases. http://wiki.cpantesters.org/wiki/SmokeTools didn't seem to have anything. I use cpan to install modules, and reading the doc discovered the -t switch, to run "make test". So out of curiosity, really, while watching TV tonight I wondered if I could hack up a quick auto tester of dev releases. My first cut works fairly well, and just does the following. First I reconfigured cpan to not prompt for CPAN::Reporter, then my script does: - get a list of recent releases (started with search.cpan.org/recent, but now discovered the RECENT-1d.json and friends, so will switch to that if I continue) - look for dev releases, only taking the most recent one - run "cpan -t <author-path-to-dist>" - I store things that I've seen in a DBM::Deep, so I don't try things more than once. Is there already something out there that does this? I don't really want to setup a CPAN mirror, I just want a low-tech way to do some automatic testing of dev releases via cron or launchd. Are there any gotchas lurking for me here? Cheers, Neil
