On Fri, Feb 16, 2001 at 04:53:19PM -0500, barries wrote: > > > What about providing a module that wraps both Pod::Tests and > > > Test::Harness, scans the command line and tests any specified modules? > > > > Well, same problem with a MakeMaker patch-- everyone will have to have > > that module. > > That's no more a burden than requiring them to have Pod::Tests in the > first place. Oh, maybe I didn't make it clear. I'm not worried about the test author having Pod::Tests, or the latest version of MakeMaker or whatever other patch/modules you need. I'm worried about those to whom the code is distributed needing the modules. Example. I write some embedded tests with Pod::Tests. Using pod2test, I generate a standard .t file and stick it into t/. I tar it all up and stick it on CPAN. Joe Bloe downloads the module and runs "make test". All the .t files are run in the usual way, including those representing my embedded tests. Joe doesn't need any extra modules or patches or anything. That's the way things should work.
