test::synopsis(3) [centos man page]

Test::Synopsis(3)					User Contributed Perl Documentation					 Test::Synopsis(3)

NAME

       Test::Synopsis - Test your SYNOPSIS code

SYNOPSIS

	 # xt/synopsis.t (with Module::Install::AuthorTests)
	 use Test::Synopsis;
	 all_synopsis_ok();

	 # Or, run safe without Test::Synopsis
	 use Test::More;
	 eval "use Test::Synopsis";
	 plan skip_all => "Test::Synopsis required for testing" if $@;
	 all_synopsis_ok();

DESCRIPTION

       Test::Synopsis is an (author) test module to find .pm or .pod files under your lib directory and then make sure the example snippet code in
       your SYNOPSIS section passes the perl compile check.

       Note that this module only checks the perl syntax (by wrapping the code with "sub") and doesn't actually run the code.

       Suppose you have the following POD in your module.

	 =head1 NAME

	 Awesome::Template - My awesome template

	 =head1 SYNOPSIS

	   use Awesome::Template;

	   my $template = Awesome::Template->new;
	   $tempalte->render("template.at");

	 =head1 DESCRIPTION

       An user of your module would try copy-paste this synopsis code and find that this code doesn't compile because there's a typo in your
       variable name $tempalte. Test::Synopsis will catch that error before you ship it.

VARIABLE DECLARATIONS

       Sometimes you might want to put some undeclared variables in your synopsis, like:

	 =head1 SYNOPSIS

	   use Data::Dumper::Names;
	   print Dumper($scalar, @array, \%hash);

       This assumes these variables like $scalar are defined elsewhere in module user's code, but Test::Synopsis, by default, will complain that
       these variables are not declared:

	   Global symbol "$scalar" requires explicit package name at ...

       In this case, you can add the following POD sequence elsewhere in your POD:

	 =for test_synopsis
	 no strict 'vars'

       Or more explicitly,

	 =for test_synopsis
	 my($scalar, @array, %hash);

       Test::Synopsis will find these "=for" blocks and these statements are prepended before your SYNOPSIS code when being evaluated, so those
       variable name errors will go away, without adding unnecessary bits in SYNOPSIS which might confuse users.

AUTHOR

       Tatsuhiko Miyagawa <miyagawa@bulknews.net>

       Goro Fuji blogged about the original idea at <http://d.hatena.ne.jp/gfx/20090224/1235449381> based on the testing code taken from
       Test::Weaken.

LICENSE

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

SEE ALSO

       Test::Pod, Test::UseAllModules, Test::Inline, Test::Snippet

perl v5.16.3							    2009-07-06							 Test::Synopsis(3)

Test::Pod(3)						User Contributed Perl Documentation					      Test::Pod(3)

NAME

       Test::Pod - check for POD errors in files

VERSION

       Version 1.48

SYNOPSIS

       "Test::Pod" lets you check the validity of a POD file, and report its results in standard "Test::Simple" fashion.

	   use Test::Pod tests => $num_tests;
	   pod_file_ok( $file, "Valid POD file" );

       Module authors can include the following in a t/pod.t file and have "Test::Pod" automatically find and check all POD files in a module
       distribution:

	   use Test::More;
	   eval "use Test::Pod 1.00";
	   plan skip_all => "Test::Pod 1.00 required for testing POD" if $@;
	   all_pod_files_ok();

       You can also specify a list of files to check, using the "all_pod_files()" function supplied:

	   use strict;
	   use Test::More;
	   eval "use Test::Pod 1.00";
	   plan skip_all => "Test::Pod 1.00 required for testing POD" if $@;
	   my @poddirs = qw( blib script );
	   all_pod_files_ok( all_pod_files( @poddirs ) );

       Or even (if you're running under Apache::Test):

	   use strict;
	   use Test::More;
	   eval "use Test::Pod 1.00";
	   plan skip_all => "Test::Pod 1.00 required for testing POD" if $@;

	   my @poddirs = qw( blib script );
	   use File::Spec::Functions qw( catdir updir );
	   all_pod_files_ok(
	       all_pod_files( map { catdir updir, $_ } @poddirs )
	   );

DESCRIPTION

       Check POD files for errors or warnings in a test file, using "Pod::Simple" to do the heavy lifting.

FUNCTIONS

   pod_file_ok( FILENAME[, TESTNAME ] )
       "pod_file_ok()" will okay the test if the POD parses correctly.	Certain conditions are not reported yet, such as a file with no pod in it
       at all.

       When it fails, "pod_file_ok()" will show any pod checking errors as diagnostics.

       The optional second argument TESTNAME is the name of the test.  If it is omitted, "pod_file_ok()" chooses a default test name "POD test for
       FILENAME".

   all_pod_files_ok( [@entries] )
       Checks all the files under @entries for valid POD. It runs all_pod_files() on directories and assumes everything else to be a file to be
       tested. It calls the "plan()" function for you (one test for each file), so you can't have already called "plan".

       If @entries is empty or not passed, the function finds all POD files in files in the blib directory if it exists, or the lib directory if
       not. A POD file is one that ends with .pod, .pl and .pm, or any file where the first line looks like a shebang line.

       If you're testing a module, just make a t/pod.t:

	   use Test::More;
	   eval "use Test::Pod 1.00";
	   plan skip_all => "Test::Pod 1.00 required for testing POD" if $@;
	   all_pod_files_ok();

       Returns true if all pod files are ok, or false if any fail.

   all_pod_files( [@dirs] )
       Returns a list of all the Perl files in @dirs and in directories below. If no directories are passed, it defaults to blib if blib exists,
       or else lib if not. Skips any files in CVS, .svn, .git and similar directories. See %Test::Pod::ignore_dirs for a list of them.

       A Perl file is:

       o   Any file that ends in .PL, .pl, .PL, .pm, .pod, or .t.

       o   Any file that has a first line with a shebang and "perl" on it.

       o   Any file that ends in .bat and has a first line with "--*-Perl-*--" on it.

       The order of the files returned is machine-dependent.  If you want them sorted, you'll have to sort them yourself.

TODO

       STUFF TO DO

       Note the changes that are being made.

       Note that you no longer can test for "no pod".

AUTHOR

       Currently maintained by David E. Wheeler, "<david@justatheory.com>".

       Originally by brian d foy.

       Maintainer emeritus: Andy Lester, "<andy at petdance.com>".

ACKNOWLEDGEMENTS

       Thanks to Andy Lester, David Wheeler, Paul Miller and Peter Edwards for contributions and to "brian d foy" for the original code.

COPYRIGHT AND LICENSE

       Copyright 2006-2010, Andy Lester. Some Rights Reserved.

       This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.16.3							    2014-06-09							      Test::Pod(3)