Hi,
I'm about to release a module using Module::Build. It subclasses
Module::Build to provide additional functionality.
It's a database abstraction module, and modules that use this module
will probably want to build themselves using my subclass.
I'd like to thuroughly test this functionality *before* I put the
module on CPAN, rather than uploading a potentially buggy version and then
having to fix the bugs (and test the fixes) by uploading new revisions.
I'm guessing that creating a mini-CPAN structure on my own system
and then popping that URL onto my cpan URLs will accomplish this goal (at
least, if all my dependancies are already installed).
Has anybody done this before? Is there a document (or even better,
test framework) detailing how? I've seen lots of stuff on how to test
modules that are already on CPAN, but haven't found anything concrete on
testing how a module will be have on CPAN before it's uploaded.
Thanks,
Tyler
