Re^2: how do you build and test your modules locally before publishing

Thanks very much for your reply davido. Exactly what I was looking for

One more little query, the perldoc command doesn't seem to have a -I switch. How should I test if the POD I've written looks ok? How is it usually done?

Comment on Re^2: how do you build and test your modules locally before publishing Download Code

Replies are listed 'Best First'.
Re^3: how do you build and test your modules locally before publishing by tobyink (Canon) on Dec 31, 2012 at 11:35 UTC
`perldoc` allows you to provide a file path rather than a module name... `perldoc File::Spec perldoc lib/Foo/Bar.pm` [download] I tend to view my pod in an 80x24 terminal to check there's no ugly line wrapping issues at that size. I also check with Test::Pod and Test::Pod::Coverage. `perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'`	[reply] [d/l] [select]
Re^3: how do you build and test your modules locally before publishing by davido (Cardinal) on Dec 31, 2012 at 04:01 UTC
Test::Pod, and Test::Pod::Coverage, if memory serves. Also, Perl::Critic: One of the elevated levels of whining will grouse at you if your POD is missing sections common to modules. I think Test::Kwalitee does some POD diving too, but half the time I can't even get it to install all of its deps. Test::Kwalitee and Test::PerlCritic should always be "author-only" tests, by the way. Dave	[reply]