Chris Dolan wrote:
> On Oct 3, 2006, at 11:13 AM, David Golden wrote:
> 
>> Given what you use, perhaps qr/AUTHOR_TEST/ is a good idea.
> 
> That's cool.  Then I could do C<if ($ENV{AUTHOR_TEST_CDOLAN}){ ... }> in
> my .t files and just set that to 1 in my .cshrc for all time.
> 
> I've seen discussion of the right env var name has been batted around
> here and on the Module::Build list a couple of times without resolution
> or blessing.  So, I hereby propose new .t boilerplate:
> 
>   use Test::More;
>   if (!$ENV{AUTHOR_TEST} && !$ENV{AUTHOR_TEST_<CPANID>}) {
>       plan skip_all => 'Author test';
>   }
>   plan ...;
> 
> where <CPANID> is either the maintainer's PAUSE username or, for large
> projects, some unique package/family identifier.  For example, my PAUSE
> ID of "CDOLAN" or a project ID like "PLAGGER" or "PERL_CRITIC" or
> "DATETIME".
> 
> People who want to be really thorough can set the AUTHOR_TEST=1 and run
> through all of the optional tests on all installed CPAN modules.  This
> should not be set on automated/smoke systems because an author test is
> one which is only needs to succeed (or perhaps only *can* succeed) on a
> developer's machine.
> 
> Chris
> 
> -- 
> Chris Dolan, Software Developer, http://www.chrisdolan.net/
> Public key: http://www.chrisdolan.net/public.key
> vCard: http://www.chrisdolan.net/ChrisDolan.vcf
> 
> 
> 
> 

Just for the sake of mentioning other things...in terms of this topic,
what is an "author" in AUTHOR_TEST_<CPANID> ?

Is that the original author? The last person who uploaded the dist? A
random author from a group of "core developers"? And how woulod I know
which ones to choose as the person using AUTHOR_TEST_<CPANID>?

Sometimes the author isn't the author, and authors change. Sometimes, a
module's "author" varies in the eyes of the public depending on who last
uploaded  the dist.

Personally, I use TEST_PRIVATE instead to avoid any implied ties like that.

But I'm silly like that. :-)

-=Chris

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to