use Perl

• Just for the sake of mentioning it... (Score:1)

  by jk2addict (4946)

  The most common variable seems to be TEST_AUTHOR. I've also seen TEST_PRIVATE, but not as much.
• Along the lines of AUTOMATED_TESTING... (Score:1)

  by dagolden (6584)

  $ENV{AUTOMATED_TESTING} is in common use to help tests change behavior when being run by a smoke testing system.

  I've seen (and have adopted myself) the use of $ENV{AUTHOR_TESTING} for the purpose you describe.
• When existing control structures are insufficient (Score:1)

  by Aristotle (5147)

  $ENV{ TEST_AUTHOR } and eval q{
      use Test::Pod::Coverage;
      goto RUN_TESTS;
  };
  
  plan skip_all => $@
      ? 'Test::Pod::Coverage not installed; skipping POD coverage'
      : 'Set TEST_AUTHOR in your environment to enable these tests';
  
  RUN_TESTS:

  GOTO is sometimes the only way to express control flow consisely.
  • Re:When existing control structures are insufficie (Score:1)

    by hex (3272)

    Swish!
• The flag you are after... (Score:1)

  by Alias (5735)

  is $ENV{AUTOMATED_TESTING} (as a few others have noted).
  
  I use this for my developer tests as well, since it's never a bad idea to have the other CPAN testers rerun your developer tests in other contexts.
  
  The other thing this can allow you to do is avoid the eval stuff and make sure you have the modules when you need them.
  
  in your Makefile.PL (assuming Module::Install in my case).
  
use strict;
use inc::Module::Install;

name 'Foo';
all_from 'lib/Foo.pm';
requires 'File::Spec' => 0;
build_requires 'Test::More' =>