Last week, while at the same Test Automation Conference Acme attended, I had an inspiration. Given that Yahoo! is using my TAPx::Parser, Torsten Shoenfeld has written a GTK front end for it (I need to include his name directly in the POD), Shlomi Fish is integrating TAPx::Parser with Test::Run, people are starting to send me patches and there's a general increase in interest for it, it's time for me to get this thing out of alpha.
How better to do that than to run TAPx::Parser against all of CPAN? Since I use CPAN::Mini, I have most of the CPAN on my hard-drive. As it turns out, testing everything isn't practical, but I can test most of it. My initial plan is to discard all Apache and Win32 specific modules, anything without a Build.PL or Makefile.PL file or a t/ directory. I might be tossing out too much, but I still have thousands of packages I can test on my iBook.
I get through about 200 of them before my code can no longer fork (something about "resource not available") and I can't even run ls in a directory until I kill my code. This has turned out to be very difficult, but I've learned a lot about my code and have already found some strange edge cases it can't handle.
In other news, Acme wants to install your tests with your code so you can test that your installation works. What a brilliant idea!