Chris Dolan wrote:
Here are the points I think are important, gleaned from people's recent
comments:
* Should have two forms: a general one and a specific one (like
AUTHOR_TEST and AUTHOR_TEST_CDOLAN)
* Should start with PERL_
* Should contain TEST or TESTING
* Should not be too long, so it doesn't need to wrap in code
* Should clearly indicate that the test is not for end users
* Should indicate that it is valuable for any contributing developers
(i.e. I don't like PRIVATE -- too forbidding)
So, I revise my proposal to:
PERL_DEV_TEST
and
PERL_DEV_TEST_<ID>
where <ID> is any string likely not to collide with other developers or
projects. It would be used like this in a .t file:
Why not just one variable, and then let the value decide what is tested:
# Run all developer tests for all modules
PERL_TEST => 1
# Run developer tests for Module::Foo and Module::Bar
PERL_TEST => 'Module::Foo,Module::Bar'
# Run developer tests for $ENV{CPANID} eq $CPANID || $ENV{USER} eq $CPANID
PERL_TEST => '<$CPANID>'
Randy.
