where <ID> is any string likely not to collide with other developers or
projects. It would be used like this in a .t file:
use strict;
use Test::More;
if (!$ENV{PERL_DEV_TEST} && !$ENV{PERL_DEV_TEST_PERLCRITIC}) {
plan skip_all => 'Developer test';
}
plan ...
Is that good enough?
I'd ideally like to keep this constrained to a single environment variable.
These tests are all the same sort of thing, tests that you run before
you release, but not otherwise. If so, there's the existing
AUTOMATED_TESTING flag.
So that would give us two options, one for general bulk testing, another
for when releasing modules.
I like the simplicity.
Adam K
