proc::test_intercept(3) [osx man page]

test_intercept(3)					User Contributed Perl Documentation					 test_intercept(3)

test User Intercept Methods
       This performs very minimal testing and was written to test some minor changes I made to Proc::Reliable so that STDERR was properly routed
       to user methods AND any left over strings were passed (those not terminated by an ending newline).

       Written by Robb Canfield <robb at canfield dot com>

       Date 2003-11-21

POD ERRORS

       Hey! The above document had some coding errors, which are explained below:

       Around line 14:
	   '=end' without a target?

perl v5.16.2							    2003-11-21							 test_intercept(3)

Test::use::ok(3)					User Contributed Perl Documentation					  Test::use::ok(3)

NAME

       Test::use::ok - Alternative to Test::More::use_ok

SYNOPSIS

	   use ok 'Some::Module';

DESCRIPTION

       According to the Test::More documentation, it is recommended to run "use_ok()" inside a "BEGIN" block, so functions are exported at
       compile-time and prototypes are properly honored.

       That is, instead of writing this:

	   use_ok( 'Some::Module' );
	   use_ok( 'Other::Module' );

       One should write this:

	   BEGIN { use_ok( 'Some::Module' ); }
	   BEGIN { use_ok( 'Other::Module' ); }

       However, people often either forget to add "BEGIN", or mistakenly group "use_ok" with other tests in a single "BEGIN" block, which can
       create subtle differences in execution order.

       With this module, simply change all "use_ok" in test scripts to "use ok", and they will be executed at "BEGIN" time.  The explicit space
       after "use" makes it clear that this is a single compile-time action.

SEE ALSO

       Test::More

CC0 1.0 Universal
       To the extent possible under law, XX has waived all copyright and related or neighboring rights to Test-use-ok.

       This work is published from Taiwan.

       <http://creativecommons.org/publicdomain/zero/1.0>

POD ERRORS

       Hey! The above document had some coding errors, which are explained below:

       Around line 45:
	   Non-ASCII character seen before =encoding in 'XX'. Assuming UTF-8

perl v5.18.2							    2012-09-11							  Test::use::ok(3)