Help-Site Computer Manuals
Software
Hardware
Programming
Networking
  Algorithms & Data Structures   Programming Languages   Revision Control
  Protocols
  Cameras   Computers   Displays   Keyboards & Mice   Motherboards   Networking   Printers & Scanners   Storage
  Windows   Linux & Unix   Mac

Maypole::CLI
Command line interface to Maypole for testing and debugging

Maypole::CLI - Command line interface to Maypole for testing and debugging


NAME

Maypole::CLI - Command line interface to Maypole for testing and debugging


SYNOPSIS


  % setenv MAYPOLE_TEMPLATES /var/www/beerdb/

  % perl -MMaypole::CLI=BeerDB -e1 http://localhost/beerdb/brewery/frontpage


DESCRIPTION

This module is used to test Maypole sites without going through a web server or modifying them to use a CGI frontend. To use it, you should first either be in the template root for your Maypole site or set the environment variable MAYPOLE_TEMPLATES to the right value.

Next, you import the Maypole::CLI module specifying your base Maypole subclass. The usual way to do this is with the -M flag: perl -MMaypole::CLI=MyApp. This is equivalent to:


    use Maypole::CLI qw(MyApp);

Now Maypole will automatically call your application's handler with the URL specified as the first command line parameter. This should be the full URL, starting from whatever you have defined as the uri_base in your application's configuration, and may include query parameters.

The Maypole HTML output should then end up on standard output.


Support for testing

The module can also be used as part of a test script.

When used programmatically, rather than from the command line, its behaviour is slightly different.

Although the URL is taken from @ARGV as normal, your application's handler method is not called automatically, as it is when used on the command line; you need to call it manually. Additionally, when handler is called, the output is not printed to standard output but stored in $Maypole::CLI::buffer, to allow you to check the contents more easily.

For instance, a test script could look like this:


    use Test::More tests => 3;

    use Maypole::CLI qw(BeerDB);

    use Maypole::Constants;

    $ENV{MAYPOLE_TEMPLATES} = "t/templates";

    # Hack because isa_ok only supports object isa not class isa

    isa_ok( (bless {},"BeerDB") , "Maypole");

    like(BeerDB->call_url("http://localhost/beerdb/";), qr/frontpage/, "Got the front page");

    like(BeerDB->call_url("http://localhost/beerdb/beer/list";), qr/Organic Best/, "Found a beer in the list");


METHODS

call_url
for use in scripts. takes an url as argument, and returns the buffer.


Implementation

This class overrides a set of methods in the base Maypole class to provide it's functionality. See Maypole for these:

get_template_root
parse_args
parse_location
send_output
warn
Programminig
Wy
Wy
yW
Wy
Programming
Wy
Wy
Wy
Wy