Re^3: Top prerequisites based on data from CPANTS

I mean that testing documentation on installation is stupid and wrong. These are tests that should be run only by the module author.

Comment on Re^3: Top prerequisites based on data from CPANTS
Re^4: Top prerequisites based on data from CPANTS by elmex (Friar) on Apr 19, 2008 at 16:30 UTC
Ah yes, I see what you mean. I don't understand why eg. kwalitee requires each distribution to have a distributed pod and pod-coverage test. Same thing with most other (usually regression) tests, eg. when you write tests for your API that doesn't depend on anything which is different from system to system. Or a protocol implementation test, also doesn't need to be distributed, or at least doesn't need to run on installation.	[reply]
Re^5: Top prerequisites based on data from CPANTS by domm (Chaplain) on Apr 19, 2008 at 18:48 UTC
I don't understand why eg. kwalitee requires each distribution to have a distributed pod and pod-coverage test. Because: it shows that the author cares about this issue if the author abandons the dist, a new maintainer gets all the stuff the previous author put into the dist it does no harm - if done right. And soon CPANTS will check if it's done right. `-- #!/usr/bin/perl for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}` [download]	[reply] [d/l]
Re^6: Top prerequisites based on data from CPANTS by Tux (Prior) on Apr 19, 2008 at 19:51 UTC
Like having these two tests in `xt/`? Enjoy, Have FUN! H.Merijn	[reply] [d/l]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks