Adriano Ferreira wrote:
> On 8/2/07, David Golden <[EMAIL PROTECTED]> wrote:
>> Having an actual pod/pod-coverage.t gives a handy place to put those
>> customizations.  Yes, some of that could be put in
>> "pod_coverage_options" in a config or a ACTION_testpod method, but to
>> me, that introduces extra complexity that I don't want cluttering
>> Build.PL.
> 
> Agreed in all manners. IMHO, Build.PL and Makefile.PL should be kept
> as dumb as possible. And easy to be read (and understood).
> 
>> Having an "authortest/" directory that gets run with a harness is
>> simple and consistent.
> 
> There is already a convention that tests go under the "t/" directory
> and also that they usually match the glob "t/*.t". I cannot think of
> anything simpler and that can possibly works, than to stick the extra
> tests into subdirectories of "t/" like chromatic does ( "t/author/*.t"
> or "t/developer/*.t" ).
> 
> The behavior could be triggered by updating M::B and EUMM to make them
> run the extended glob "t/**/*.t" when PERL_AUTHOR_TESTING or
> AUTOMATED_TESTING is setted.
> 
> Even programmers unaware of such conventions that are trying with the
> distribution, will make
> 
> $ prove t/author/pod.t
> 
> naturally as he/she runs any other tests.
> 
>> Regards,
>> David
>>
> 
> 

I must say, I like t/author more than t/authortests...

However, my main beef overall is now we essentially have a 'reserved
name' directory that may interfere with how I may choose to group tests
for larger distributions.

For example, I have a boatload of tests to test http server code in
t/live, and tests to test providers in t/providers and tests to test
catalyst in...shockingly...t/catalyst, etc...

If I have a boatload of tests for a 'author' object, I might choose to
group then in t/author

Sure, it's rare. Sure, I could name all those tests t/author_*.t...
Either way, I think just assuming a directory name is rude.

Now, if there were a way to tell the harness which directory to consider
as 'author' tests.. then I guess I don't care.

-=Chris


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to