On Thu, Feb 02, 2006 at 02:56:09AM -0800, Tyler MacDonald wrote: > A new module doesn't need to be added to the core, so long as there > is a way that we can reliably detect when a person wishes to build and test > any given perl package for an objectively unselfish purpose such as > 1:prepackaging, 2:automated testing, or 3:releasing. All three are viral so > it's best to make sure they do no harm, while still maintaining some level > of convenience for the "end user". > > There's already AUTOMATED_TESTING for 2 and "make disttest" for #3 > (just keep a file around in your repo that's not in your MANIFEST and test > for it's presence.) > > Any good way to detect #1?
An environment variable. PERL_TEST_EXHAUSTIVE? And make/Build disttest can set it too. In the perl core, the few tests that are normally not run are requested by a -torture switch. But I think despite this precedent exhaustive sounds better. But please, lets not have new ta/ or whatever directories or .ta files; this is a problem that is well taken care of with skip_all. If somebody really wants, they could go the Test::Exhaustive route, which would automatically do the skip_all if the env vars weren't set. But putting a few stock lines at the start of your .t file isn't really all that big a deal.
