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.
  • Since CPAN::Reporter I have toyed with the idea of becoming a tester… however, all I have to test on is my dev machine, a bog-standard Slackware 12.0 machine, ie. an unthreaded 5.8.8 on 32-bit x86 Linux, with my particular mix of required modules installed among the system perl. I wouldn’t set up any sort of controlled environment. I wouldn’t be going out of my way to generate test reports either – just send the occasional one when I install something.

    And I have to wonder if that

    • Occasionally, for whatever reason some distributions do miss out. Usually because they require libraries that the testers don't have installed, or they filter out some distributions due to problems with test them (e.g. I couldn't test Apache modules on Win32). So even if you do have a common setup, it is still possible for you to find a failure that hasn't been found by other testers. Whether you only submit 1 report a month or hundreds, it all helps :)

      Also because you don't have a minimal "fresh" installation environment like the prolific testers, you are more likely to experience issues that regular users would experience with installations, which are of value to authors too.