On 8/2/07, Eric Wilhelm <[EMAIL PROTECTED]> wrote: > For such usage, extra dependencies would only be optional in extreme > cases. Further, pod/pod-coverage would possibly even be 'assumed' > tests. That is, why bother even having a .t file if the authortest > tool knows how to run testpod and testpodcoverage?
Who says I keep my POD in same file as my code? I might put it in a separate file that has a completely different name. Or I might have a different convention for private vs public methods, etc. Having an actual pod/pod-coverage.t gives a handy place to put those customizations. Yes, some of that could be put in "pod_coverage_options" in a config or a ACTION_testpod method, but to me, that introduces extra complexity that I don't want cluttering Build.PL. Having an "authortest/" directory that gets run with a harness is simple and consistent. Regards, David
