The task of testing CPAN distributions is largely automated. What the Perl community is looking for from you is to provide hardware, the more unusual the better. However,there are certain platforms that CPANPLUS has issues on.

What tasks are you expected to perform?

Once you have CPANPLUS and associated modules installed, it's a matter of detecting new distributions that have been uploaded, and doing a CPANPLUS test install, mailing back the test results. All of this is automated.

You are expected to join and take part in the cpan-testers mailing list

What level of experience do you need to have?

In many ways, the naive user's approach with no technical input may be useful - finding issues that "seemed obvious", and detecting documentation errors. However, the ability to diagnose scripting and install problems is useful - differentiating problems on the test bed from problems with the module being tested.

what is the expected commitment in terms of time?

As the scripts are automated, you would be expected to support your test bed and deal with any idiosyncracies. Some of the more dedicated testers do analysis of failing tests, and give extra clues to the module author. This is something I regard as beyond the call of duty, but occasionally most welcome.

--

Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)

In reply to Re: What is involved in being a cpan tester? by rinceWind
in thread What is involved in being a cpan tester? by richill

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.