# from Philippe Bruhat (BooK)
# on Thursday 05 April 2007 02:29 am:
>No, I've already solved that problem by putting the tests in separate
>directories. E.g., I've now a single pod.t file in test/pod that
>will use Test::Pod on all the files in cwd (or the files passed as
>command line parameters to the test script).
Seems like one good installable tool to test pod would be preferable to
creating multiple copies of a test script. Perhaps something like a
podprove (and maybe it could do podcoverage and podspelling too.)
`./Build testpod` seems to be all we have at the moment.
--Eric
--
"...our schools have been scientifically designed to
prevent overeducation from happening."
--William Troy Harris
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
