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.

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]

Like having these two tests in xt/?


Enjoy, Have FUN! H.Merijn