test::http::server::simple::stashwarnings(3pm) [debian man page]

Test::HTTP::Server::Simple::StashWarnings(3pm)		User Contributed Perl Documentation	    Test::HTTP::Server::Simple::StashWarnings(3pm)

NAME

       Test::HTTP::Server::Simple::StashWarnings - catch your forked server's warnings

SYNOPSIS

	   package My::Webserver::Test;
	   use base qw/Test::HTTP::Server::Simple::StashWarnings My::Webserver/;

	   sub test_warning_path { "/__test_warnings" }

	   package main;
	   use Test::More tests => 42;

	   my $s = My::WebServer::Test->new;

	   my $url_root = $s->started_ok("start up my web server");

	   my $mech = WWW::Mechanize->new;

	   $mech->get("$url_root/some_action");

	   $mech->get("/__test_warnings");
	   my @warnings = My::WebServer::Test->decode_warnings($mech->content);
	   is(@warnings, 0, "some_action gave no warnings");

DESCRIPTION

       Warnings are an important part of any application. Your web application should warn the user when something is amiss.

       Almost as importantly, we want to be able to test that the web application gracefully copes with bad input, the back button, and all other
       aspects of the user experience.

       Unfortunately, tests seldom cover what happens when things go poorly. Are you "sure" that your application checks authorization for that
       action? Are you "sure" it will tomorrow?

       This module lets you retrieve the warnings that your forked server throws. That way you can test that your application continues to throw
       warnings when it makes sense. Catching the warnings also keeps your test output tidy. Finally, you'll be able to see when your application
       throws new, unexpected warnings.

SETUP

       The way this module works is it catches warnings and makes them available on a special URL (which must be defined by you in the
       "test_warning_path" method).  You can use "WWW::Mechanize" (or whichever HTTP agent you prefer) to download the warnings. The warnings will
       be serialized. Use decode_warnings to get the list of warnings seen so far (since last request anyway).

       Warnings are encoded using Storable by default, but your subclass may override the "encode_warnings" and "decode_warnings" methods.

TIPS

       Setting the "TEST_VERBOSE" environment variable to a true value will cause warnings to be displayed immediately, even if they would be
       captured and tested later.

AUTHOR

       Shawn M Moore, "<sartak at bestpractical.com>"

BUGS

       Please report any bugs or feature requests to "bug-test-http-server-simple-stashwarnings at rt.cpan.org", or through the web interface at
       <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=test-http-server-simple-stashwarnings>.

COPYRIGHT &; LICENSE
       Copyright 2008 Best Practical Solutions.

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

perl v5.10.0							    2009-07-07			    Test::HTTP::Server::Simple::StashWarnings(3pm)

Test::WWW::Mechanize::CGIApp(3pm)			User Contributed Perl Documentation			 Test::WWW::Mechanize::CGIApp(3pm)

NAME

       Test::WWW::Mechanize::CGIApp - Test::WWW::Mechanize for CGI::Application

SYNOPSIS

	 # We're in a t/*.t test script...
	 use Test::WWW::Mechanize::CGIApp;

	 my $mech = Test::WWW::Mechanize::CGIApp->new;

	 # test a class that uses CGI::Application calling semantics.
	 # (in this case we'll new up an instance of the app and call
	 # its ->run() method)
	 #
	 $mech->app("My::WebApp");
	 $mech->get_ok("?rm=my_run_mode&arg1=1&arg2=42");

	 # test a class that uses CGI::Application::Dispatch
	 # to locate the run_mode
	 # (in this case we'll just call the ->dispatch() class method).
	 #
	 my $dispatched_mech = Test::WWW::Mechanize::CGIApp->new;
	 $dispatched_mech->app("My::DispatchApp");
	 $mech->get_ok("/WebApp/my_run_mode?arg1=1&arg2=42");

	 # create an anonymous sub that this class will use to
	 # handle the request.
	 #
	 # this could be useful if you need to do something novel
	 # after creating an instance of your class (e.g. the
	 # fiddle_with_stuff() below) or maybe you have a unique
	 # way to get the app to run.
	 #
	 my $custom_mech = Test::WWW::Mechanize::CGIApp->new;
	 $custom_mech->app(
	    sub {
	      require "My::WebApp";
	      my $app = My::WebApp->new();
	      $app->fiddle_with_stuff();
	      $app->run();
	    });
	 $mech->get_ok("?rm=my_run_mode&arg1=1&arg2=42");

	 # at this point you can play with all kinds of cool
	 # Test::WWW::Mechanize testing methods.
	 is($mech->ct, "text/html");
	 $mech->title_is("Root", "On the root page");
	 $mech->content_contains("This is the root page", "Correct content");
	 $mech->follow_link_ok({text => 'Hello'}, "Click on Hello");
	 # ... and all other Test::WWW::Mechanize methods

DESCRIPTION

       This package makes testing CGIApp based modules fast and easy.  It takes advantage of Test::WWW::Mechanize to provide functions for common
       web testing scenarios. For example:

	 $mech->get_ok( $page );
	 $mech->title_is( "Invoice Status",
			  "Make sure we're on the invoice page" );
	 $mech->content_contains( "Andy Lester", "My name somewhere" );
	 $mech->content_like( qr/(cpan|perl).org/,
			     "Link to perl.org or CPAN" );

       For applications that inherit from CGI::Application it will handle requests by creating a new instance of the class and calling its "run"
       method.	For applications that use CGI::Application::Dispatch it will call the "dispatch" class method.	If neither of these options are
       the right thing, you can set a reference to a sub that will be used to handle the request.

       This module supports cookies automatically.

       Check out Test::WWW::Mechanize for more information about all of the cool things you can test!

CONSTRUCTOR

       new

       Behaves like, and calls, Test::WWW::Mechanize's "new" method.  It optionally uses an "app" parameter (see below), any other parameters get
       passed to Test::WWW::Mechanize's constructor. Note that you can either pass the name of the CGI::Application into the constructor using the
       "app" parameter or set it later using the "app" method.

	 use Test::WWW::Mechanize::CGIApp;
	 my $mech = Test::WWW::Mechanize::CGIApp->new;

	 # or

	 my $mech = Test::WWW::Mechanize::CGIApp->new(app => 'TestApp');

METHODS

       $mech->app($app_handler)

       This method provides a mechanism for informing Test::WWW::Mechanize::CGIApp how it should go about executing your run_mode.  If you set it
       to the name of a class, then it will load the class and either create an instance and ->run() it (if it's CGI::Application based), invoke
       the ->dispatch() method if it's CGI::Application::Dispatch based, or call the supplied anonymous subroutine and let it do all of the heavy
       lifting.

SEE ALSO

       Related modules which may be of interest: Test::WWW::Mechanize, WWW::Mechanize.

       Various implementation tricks came from Test::WWW::Mechanize::Catalyst.

AUTHOR

       George Hartzell, "<hartzell@alerce.com>"

       based on Test::WWW::Mechanize::Catalyst by Leon Brocard, "<acme@astray.com>".

COPYRIGHT

       Copyright (C) 2007, George Hartzell

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

perl v5.8.8							    2008-03-12					 Test::WWW::Mechanize::CGIApp(3pm)