Eric Wilhelm wrote: > # from David Golden > # on Monday 30 July 2007 05:34 am: > >> The issue at hand is really *release* testing (i.e. did I bump the >> version, did I test my Pod, do I use good style, etc.) being mixed >> with *functional* testing -- and the corresponding push for release >> testing modules being included as requirements. > > Yes. We want to know that the author tested the code and went through > the checklist before the release. We would like to be able to verify > it ourselves, but we don't want all of that to get in the way of > installation.
Ok, I can agree with that.
>
>> For that, I blame -- among other things -- Module::Starter for
>> including pod.t and pod-coverage.t and with a default setting to run
>> tests. Better would have been to skip tests unless
>> $ENV{AUTHOR_TESTING} or some similar flag was set.
>
> Again, yes. Though I'm going to stick with "delete them."
>
> I think the important bit is that `make test` only runs tests which
> verify the module's functionality.
>
> Anything else needs to be a separate test target or out-of-band tool.
I don't agree. What runs when I do 'make test' is up to me, and if I
want to litter it up with 'author' tests, then that's my business; right
or wrong. Don't like it, then don't use my modules. (I still think all
author tests should not run by default...)
What needs to be unencumbered is:
perl Makefile.PL (should not reference non-functional modules in prereq)
make install (just install it please)
Any notion that make test needs to be altered, or should or shouldn't
run some and not other 'tests' is silly imho.
Putting Test::Foo in PREREQ=Bad. Fine. I understand.
Bitching about how many and what tests get run during 'make test' is absurd.
Of course, I could be missing the point of it all.
signature.asc
Description: OpenPGP digital signature
