Hi there: On Sun, Aug 2, 2009 at 9:49 AM, Shawn H. Corey<[email protected]> wrote: > Hi, > > I have a module, Sub::Starter, which I have prepared for CPAN. I think I > have all the right goodies in the right places. But I am worried that I > might be missing something important. And yes, I read the documentation, > that is, what I could find. The thing is that documentation isn't always > kept up to date. So I thought I'd ask the experts. > > Here is a copy of my MANIFEST. Is there anything missing? > > Build.PL > Changes > MANIFEST > README > lib/Sub/Starter.pm > script/substarter > t/00-load.t > t/01-parse_usage.t > t/02-usage.t > t/03-sub.t > t/04-pod.t > t/pod-coverage.t > t/pod.t
Why is there both a 04-pod.t and a t/pod.t? Are they the same test? Also, you may want to model those tests after what Alias does with his distributions (RELEASE_TESTING and AUTOMATED_TESTING) unless you have already done so. Module::Install is said to have a feature implemented (at some point in the future) which will help write author tests like pod-coverage, the Test::MinimumVersion test (to detect the minimum perl version required to run your code), etc. You may also wish to supply a Makefile.PL (via Module::Build::Compat) to support older perls/CPAN.pm's. There is also a list of criteria on CPANTS (http://cpants.perl.org) I would definitely suggest replicating Alias' test code, see: http://cpansearch.perl.org/src/ADAMK/ORDB-CPANMeta-0.10/t/ In particular, the 9*.t series of tests are important/useful. > > > -- > Just my 0.00000002 million dollars worth, > Shawn > > Programming is as much about organization and communication > as it is about coding. > > My favourite four-letter word is "Done!" >
