test::builder::module(3) [centos man page]

Test::Builder::Module(3)				User Contributed Perl Documentation				  Test::Builder::Module(3)

NAME

       Test::Builder::Module - Base class for test modules

SYNOPSIS

	 # Emulates Test::Simple
	 package Your::Module;

	 my $CLASS = __PACKAGE__;

	 use base 'Test::Builder::Module';
	 @EXPORT = qw(ok);

	 sub ok ($;$) {
	     my $tb = $CLASS->builder;
	     return $tb->ok(@_);
	 }

	 1;

DESCRIPTION

       This is a superclass for Test::Builder-based modules.  It provides a handful of common functionality and a method of getting at the
       underlying Test::Builder object.

   Importing
       Test::Builder::Module is a subclass of Exporter which means your module is also a subclass of Exporter.	@EXPORT, @EXPORT_OK, etc...  all
       act normally.

       A few methods are provided to do the "use Your::Module tests =" 23> part for you.

       import

       Test::Builder::Module provides an import() method which acts in the same basic way as Test::More's, setting the plan and controlling
       exporting of functions and variables.  This allows your module to set the plan independent of Test::More.

       All arguments passed to import() are passed onto "Your::Module->builder->plan()" with the exception of "import =>[qw(things to import)]".

	   use Your::Module import => [qw(this that)], tests => 23;

       says to import the functions this() and that() as well as set the plan to be 23 tests.

       import() also sets the exported_to() attribute of your builder to be the caller of the import() function.

       Additional behaviors can be added to your import() method by overriding import_extra().

       import_extra

	   Your::Module->import_extra(@import_args);

       import_extra() is called by import().  It provides an opportunity for you to add behaviors to your module based on its import list.

       Any extra arguments which shouldn't be passed on to plan() should be stripped off by this method.

       See Test::More for an example of its use.

       NOTE This mechanism is VERY ALPHA AND LIKELY TO CHANGE as it feels like a bit of an ugly hack in its current form.

   Builder
       Test::Builder::Module provides some methods of getting at the underlying Test::Builder object.

       builder

	 my $builder = Your::Class->builder;

       This method returns the Test::Builder object associated with Your::Class.  It is not a constructor so you can call it as often as you like.

       This is the preferred way to get the Test::Builder object.  You should not get it via "Test::Builder->new" as was previously recommended.

       The object returned by builder() may change at runtime so you should call builder() inside each function rather than store it in a global.

	 sub ok {
	     my $builder = Your::Class->builder;

	     return $builder->ok(@_);
	 }

perl v5.16.3							    2011-02-23						  Test::Builder::Module(3)

Plack::Builder(3pm)					User Contributed Perl Documentation				       Plack::Builder(3pm)

NAME

       Plack::Builder - OO and DSL to enable Plack Middlewares

SYNOPSIS

	 # in .psgi
	 use Plack::Builder;

	 my $app = sub { ... };

	 builder {
	     enable "Deflater";
	     enable "Session", store => "File";
	     enable "Debug", panels => [ qw(DBITrace Memory Timer) ];
	     enable "+My::Plack::Middleware";
	     $app;
	 };

	 # use URLMap

	 builder {
	     mount "/foo" => builder {
		 enable "Foo";
		 $app;
	     };

	     mount "/bar" => $app2;
	     mount "http://example.com/" => builder { $app3 };
	 };

	 # using OO interface

	 my $builder = Plack::Builder->new();
	 $builder->add_middleware('Foo', opt => 1);
	 $app = $builder->mount('/app' => $app);
	 $app = $builder->to_app($app);

DESCRIPTION

       Plack::Builder gives you a quick domain specific language (DSL) to wrap your application with Plack::Middleware subclasses. The middleware
       you're trying to use should use Plack::Middleware as a base class to use this DSL, inspired by Rack::Builder.

       Whenever you call "enable" on any middleware, the middleware app is pushed to the stack inside the builder, and then reversed when it
       actually creates a wrapped application handler. "Plack::Middleware::" is added as a prefix by default. So:

	 builder {
	     enable "Foo";
	     enable "Bar", opt => "val";
	     $app;
	 };

       is syntactically equal to:

	 $app = Plack::Middleware::Bar->wrap($app, opt => "val");
	 $app = Plack::Middleware::Foo->wrap($app);

       In other words, you're supposed to "enable" middleware from outer to inner.

INLINE MIDDLEWARE

       Plack::Builder allows you to code middleware inline using a nested code reference.

       If the first argument to "enable" is a code reference, it will be passed an $app and is supposed to return another code reference which is
       PSGI application that consumes $env in runtime. So:

	 builder {
	     enable sub {
		 my $app = shift;
		 sub {
		     my $env = shift;
		     # do preprocessing
		     my $res = $app->($env);
		     # do postprocessing
		     return $res;
		 };
	     };
	     $app;
	 };

       is equal to:

	 my $mw = sub {
	     my $app = shift;
	     sub { my $env = shift; $app->($env) };
	 };

	 $app = $mw->($app);

URLMap support
       Plack::Builder has a native support for Plack::App::URLMap with "mount" method.

	 use Plack::Builder;
	 my $app = builder {
	     mount "/foo" => $app1;
	     mount "/bar" => builder {
		 enable "Foo";
		 $app2;
	     };
	 };

       See Plack::App::URLMap's "map" method to see what they mean. With builder you can't use "map" as a DSL, for the obvious reason :)

       NOTE: Once you use "mount" in your builder code, you have to use "mount" for all the paths, including the root path ("/"). You can't have
       the default app in the last line of "builder" like:

	 my $app = sub {
	     my $env = shift;
	     ...
	 };

	 builder {
	     mount "/foo" => sub { ... };
	     $app; # THIS DOESN'T WORK
	 };

       You'll get warnings saying that your mount configuration will be ignored. Instead you should use "mount "/" => ..." in the last line to set
       the default fallback app.

	 builder {
	     mount "/foo" => sub { ... };
	     mount "/" => $app;
	 }

       Note that the "builder" DSL returns a whole new PSGI application, which means

       o   "builder { ... }" should normally the last statement of a ".psgi" file, because the return value of "builder" is the application that
	   actually is executed.

       o   You can nest your "builder" block, mixed with "mount" (see URLMap support above):

	     builder {
		 mount "/foo" => builder {
		     mount "/bar" => $app;
		 }
	     }

	   will locate the $app under "/foo/bar" since the inner "builder" block puts it under "/bar" and it results a new PSGI application which
	   is located under "/foo" because of the outer "builder" block.

CONDITIONAL MIDDLEWARE SUPPORT

       You can use "enable_if" to conditionally enable middleware based on the runtime environment. See Plack::Middleware::Conditional for
       details.

SEE ALSO

       Plack::Middleware Plack::App::URLMap Plack::Middleware::Conditional

perl v5.14.2							    2012-05-17						       Plack::Builder(3pm)