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.
  • There are currently around 60 regular CPAN Testers, who test on a variety of platforms and perls. Last month there were 22 different platforms and 11 different perls giving 241 different setups. Being able to have perhaps a good selection of images, with at least the major perl releases and the most popular platforms is a good idea. And the idea you're proposing would hopefully catch most of the obvious bugs, but you aren't going to get away from using CPAN testers. I am pretty certain every single one of t
    • CPAN Testers doesn't solve the problem of testing. Full stop.

      They solve ONLY the limited subset "testing released CPAN packages".

      CPAN Testers is no solution at all for company or private packages.

      And of course they test only what they want. If they didn't want to be in CPAN testers, they wouldn't be there.

      They have full control over what they do, and I have ZERO control over them, as you would expect from people contributing their time in this way.

      I'm just starting to get a little frustrated that every time I move into a new area of CPAN, I have to rewrite to replace half of what I encounter because a lot of it is written for far too specific scenarios.

      And I'm REALLY annoyed at people that ACT like they are volunteering, and then proceed to troll and generally act like people with "Bad Head"s (google it)
      • CPAN Testers doesn't solve the problem of testing. Full stop.

        No it does solve complete coverage of testing, but it goes a long way to covering the bulk of scenarios. Trying to test every scenario that exists is a huge task and one I don't think will ever be achieved.

        CPAN Testers is no solution at all for company or private packages.

        Why? I assume you're talking from your own experience. In my experience the cpan-testers have proved useful to know what works on various platforms out of the box and what

      • Don't you think that a "company or private package" only has to work in the "company or private" environment and that consequently the "company or private" developer can, if he likes, use exactly the same tools as the CPAN testers to do his testing?