Actually, for those of us who support 'deep' backwards compatibility for their modules, Test::More itself is problematic. If you blindly 'use' it, you can break 5.005 compatibility for people running very old installations that lack Test::More.
Since I wasn't specifically aware of the 'misversioned dependancy' problem with Test::Pod::Coverage, I have not yet written defensive code for it. I have written defensive code for Test::More (example taken from my Class::NamedParms module):
use strict; use lib ('./blib','../blib', './lib', '../lib'); eval { require Test::More; }; if ($@) { $|++; print "1..0 # Skipped: Test::More required for testing POD coverag +e\n"; exit; } eval { require Test::Pod::Coverage; }; if ($@ or (not defined $Test::Pod::Coverage::VERSION) or ($Test::Pod:: +Coverage::VERSION < 1.06)) { Test::More::plan (skip_all => "Test::Pod::Coverage 1.06 required f +or testing POD coverage"); exit; } Test::More::plan (tests => 1); Test::Pod::Coverage::pod_coverage_ok( 'Class::NamedParms', { also_priv +ate => ['DEBUG'] });
In reply to Re: Careful with Test::Pod::Coverage. And with Test::More
by snowhare
in thread Careful with Test::Pod::Coverage
by xdg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |