Re: [Module::Build] [RFC] author tests

[Marvin H. <ma...@re...>]

On Feb 2, 2006, at 7:49 AM, Chris Dolan wrote:
> I'm specifically talking about author tests, NOT packager tests.

+1 on the idea of author tests.  I don't have strong opinions about  
the implementation.

For one of my distros, there's a script ./bin/test_valgrind.plx,  
which runs all the other tests under valgrind (this is an XS distro)  
and kicks out a log file for me to peruse.  Haven't quite figured out  
how to run it under Test::More, but that's how it ought to work, and  
it is clearly an author test, not a standard test, since it takes  
forever and depends upon the presence of valgrind.  There's also a ./ 
bin/test_tidiness.plx, which does a perltidy check on each .pm/.pod  
file -- which takes a while, depends upon perltidy, and is pointless  
after release for the same reason that checking pod is pointless  
after release.

If there had been a standardized procedure for me to follow, these  
scripts would be in a more sensible place than ./bin, and it would be  
more apparent what they're there for.  Also, if there had been a  
procedure for running all of them, they'd get run more reliably -- on  
the latest release I remembered to run the valgrind tests, but forgot  
the perltidy tests.

Marvin Humphrey
Rectangular Research
http://www.rectangular.com/