Chris Dolan wrote:
On Oct 3, 2006, at 11:04 PM, Adam Kennedy wrote:
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.
OK, I can accept that. It sacrifices a small convenience for elegance.
Then my one remaining itch is your use of the term "release". These
tests are run frequently during development, not just at release time.
That's why I've been calling them author tests or developer tests. Yes,
they are often prereqs for release, but do we want to tie them that
intimately to release? After all, some modules never get released...
I was thinking in terms of "These are the tests that you run before the
module is unleashed on the general world".
If you don't actually do them fine, but they are the standard you aim for.
As for specific authors, I'm happy if it's an OR.
As in ( $ENV{AUTHOR_TESTS} or $ENV{AUTHOR_TESTS_NAME} )
Because the only one we need document is AUTHOR_TESTS.
Remember not everyone has a CPAN login, nor should we encourage them to
if they aren't releasing to CPAN.
If I happen to use AUTHOR_TESTS_ADAMK, then I guess other than
documenting that the namespace after AUTHOR_TESTS_... is reserved for
private use, we don't need to care otherwise.
Adam K
