ALT Linux repos
S: | 1.10-alt1 |
5.0: | 1.08-alt3 |
4.1: | 1.08-alt2 |
4.0: | 1.08-alt2 |
3.0: | |
+backports: | 1.08-alt0.M30 |
Group :: Development/Perl
RPM: perl-Test-Pod-Coverage
Main Changelog Spec Patches Sources Download Gear Bugs and FR Repocop
Current version: 1.08-alt0.M30
Build date: 27 october 2006, 23:49 ( 914.1 weeks ago )
Size: 11.46 Kb
Home page: http://www.cpan.org
License: Artistic
Summary: Test-Pod-Coverage - Check for pod coverage in your distribution
Description:
List of contributors List of rpms provided by this srpm:
ACL:
Build date: 27 october 2006, 23:49 ( 914.1 weeks ago )
Size: 11.46 Kb
Home page: http://www.cpan.org
License: Artistic
Summary: Test-Pod-Coverage - Check for pod coverage in your distribution
Description:
Checks for POD coverage in files for your distribution.
use Test::Pod::Coverage tests=>1;
pod_coverage_ok( "Foo::Bar", "Foo::Bar is covered" );
Can also be called with Pod::Coverage parms.
use Test::Pod::Coverage tests=>1;
pod_coverage_ok(
"Foo::Bar",
{ also_private => [ qr/^[A-Z_]+$/ ], },
"Foo::Bar, with all-caps functions as privates",
);
The Pod::Coverage parms are also useful for subclasses that don't
re-document the parent class's methods. Here's an example from
Mail::SRS.
pod_coverage_ok( "Mail::SRS" ); # No exceptions
my $trustme = { trustme => [qr/^(new|parse|compile)$/] };
pod_coverage_ok( "Mail::SRS::DB", $trustme );
pod_coverage_ok( "Mail::SRS::Guarded", $trustme );
pod_coverage_ok( "Mail::SRS::Reversable", $trustme );
pod_coverage_ok( "Mail::SRS::Shortcut", $trustme );
If you want POD coverage for your module, but don't want to make
Test::Pod::Coverage a prerequisite for installing, create the following
as your t/pod-coverage.t file:
use Test::More;
eval "use Test::Pod::Coverage";
plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@;
plan tests => 1;
pod_coverage_ok( "Pod::Master::Html");
Finally, Module authors can include the following in a t/pod-coverage.t
file and have "Test::Pod::Coverage" automatically find and check all
modules in the module distribution:
use Test::More;
eval "use Test::Pod::Coverage 1.00";
plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@;
all_pod_coverage_ok();
Current maintainer: Vitaly Lipatov use Test::Pod::Coverage tests=>1;
pod_coverage_ok( "Foo::Bar", "Foo::Bar is covered" );
Can also be called with Pod::Coverage parms.
use Test::Pod::Coverage tests=>1;
pod_coverage_ok(
"Foo::Bar",
{ also_private => [ qr/^[A-Z_]+$/ ], },
"Foo::Bar, with all-caps functions as privates",
);
The Pod::Coverage parms are also useful for subclasses that don't
re-document the parent class's methods. Here's an example from
Mail::SRS.
pod_coverage_ok( "Mail::SRS" ); # No exceptions
my $trustme = { trustme => [qr/^(new|parse|compile)$/] };
pod_coverage_ok( "Mail::SRS::DB", $trustme );
pod_coverage_ok( "Mail::SRS::Guarded", $trustme );
pod_coverage_ok( "Mail::SRS::Reversable", $trustme );
pod_coverage_ok( "Mail::SRS::Shortcut", $trustme );
If you want POD coverage for your module, but don't want to make
Test::Pod::Coverage a prerequisite for installing, create the following
as your t/pod-coverage.t file:
use Test::More;
eval "use Test::Pod::Coverage";
plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@;
plan tests => 1;
pod_coverage_ok( "Pod::Master::Html");
Finally, Module authors can include the following in a t/pod-coverage.t
file and have "Test::Pod::Coverage" automatically find and check all
modules in the module distribution:
use Test::More;
eval "use Test::Pod::Coverage 1.00";
plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@;
all_pod_coverage_ok();
List of contributors List of rpms provided by this srpm:
- perl-Test-Pod-Coverage