use Test::More;

eval "use Test::Pod::Coverage";
plan skip_all => "Test::Pod::Coverage required for testing pod coverag
+e" if $@;

my @modules = grep{!/^Exclude::ME::General$/} all_modules();
plan tests => scalar @modules;
pod_coverage_ok($_) for @modules;
[download]

thanks!

Here's update, based on Module::New

use strict;
use warnings;
use Test::More;

eval "use Test::Pod::Coverage 1.04";
plan skip_all => 'Test::Pod::Coverage 1.04 required' if $@;
plan skip_all => 'set TEST_POD to enable this test' unless $ENV{TEST_P
+OD};
[download]

The idea is that only module developers would be interested in pod/coverage tests

#!/usr/bin/perl

use strict;
use warnings;
use Test::More tests => 2;

BEGIN {
    use_ok( 'Test::Pod::Coverage' );
}

SKIP: { 
    eval { require some::module };
    
    skip "no pod available", 1 if $@;
    
    my $module = new some::module;
    isa_ok( $module, 'some::module' );
    
    $module->test_some( "modules" );
    is( $module->errors, 0, "No errors in modules" );
}
[download]

Why? A skip block wouldn't change Test::Pod::Coverage behaviour.