cpantesters should never set AUTHOR_TESTING

[Andreas J. Koenig]

Dear fellow testers,

please don't set environment variables that could lead to extraordinary
testing conditions. Especially vulnerable environment variables are
AUTHOR_TESTING, PERL_TEST_CRITIC, PERL_TEST_POD.

Many software writers seem to use these variables to scratch their own,
private itch during testing. They enable tests that only work under
certain conditions or will become regular tests at some point in time
later or are insecure to run elsewhere and what not. The results of such
tests usually cannot be interpreted without being the author and they
are of no interest to us, the rest of the world.

When cpantesters use these variables they are pretending that the only
the author is testing privately and the world isn't looking. But
cpantesters is about the world IS looking.

Please remove these environment variables from your testbed now.

Thank you,
--
andreas

[Chris 'BinGOs' Williams]

On Thu, Dec 24, 2009 at 08:47:07AM +0100, Andreas J. Koenig wrote:
> Dear fellow testers,
>
> please don't set environment variables that could lead to extraordinary
> testing conditions. Especially vulnerable environment variables are
> AUTHOR_TESTING, PERL_TEST_CRITIC, PERL_TEST_POD.
>

> Please remove these environment variables from your testbed now.

I don't ever set these, but just in case they are accidently set and
so get propagated down to smoke processes I've just amended
POE::Component::SmokeBox to scrub these environment vars when spawning
the smoker processes.

Version 0.34 just uploaded to PAUSE.

Cheers,

--
Chris Williams
aka BinGOs
PGP ID 0x4658671F
http://www.gumbynet.org.uk
==========================