Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Re^2: Does something like Pod::Coverage::Moose exist for Moo?

by jds17 (Pilgrim)
on Oct 24, 2012 at 22:02 UTC ( #1000727=note: print w/replies, xml ) Need Help??

in reply to Re: Does something like Pod::Coverage::Moose exist for Moo?
in thread Does something like Pod::Coverage::Moose exist for Moo?

Thank you for replying again, tobyink. The reason I am using Moo(::Role) is that I want to ensure at compile time that certain classes provide a given set of methods. (For each DBMS to be supported, there is one such class handling DBMS specific things.)

Since I wanted the module to be as portable as possible, I wanted it to have few dependencies, so Moo won against Moose.

You are right, pod coverage is mainly of interest to the author(s) of a module, so I could leave the pod coverage tests out for distribution, but I am not completely happy with having two versions of the module.

Maybe I will take the time and see how Pod::Coverage::Moose works and if I can borrow from there without having to use Moose. But right now I want to get the first version of the module out as soon as possible, there is only some documentation left to be written. For the time being, I think it would be wisest to follow your suggestion and leave the coverage tests out for the users.

  • Comment on Re^2: Does something like Pod::Coverage::Moose exist for Moo?

Replies are listed 'Best First'.
Re^3: Does something like Pod::Coverage::Moose exist for Moo?
by tobyink (Abbot) on Oct 25, 2012 at 00:36 UTC

    You may have missed my point. You don't need to borrow stuff from Pod::Coverage::Moose, because Pod::Coverage::Moose already seems to support Moo classes and roles.

    Just use Pod::Coverage::Moose as-is, but put the tests in your xt directory instead of t. That way, MakeMaker (or whatever you're using to package your distribution) should find and run the test while it's building the distribution tarball, but the test will not automatically run on end users' systems.

    perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'

      Oh, I really have missed your point. It's the first time I want to publish a module so this packaging question did not turn up before.

      I will try to use Pod::Coverage::Moose and put the author tests in xt. I found a nice description of handling author tests when using Module::Build here: Thank you for putting me on the right track!

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1000727]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (3)
As of 2018-03-25 04:10 GMT
Find Nodes?
    Voting Booth?
    When I think of a mole I think of:

    Results (300 votes). Check out past polls.