| Name : perl-Test-WWW-Mechanize-Catalyst
| |
| Version : 0.620.0
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : 1.4
| Date : 2019-02-19 07:31:51
|
| Group : Unspecified
| Source RPM : perl-Test-WWW-Mechanize-Catalyst-0.620.0-1.4.src.rpm
|
| Size : 0.04 MB
| |
| Packager : (none)
| |
| Summary : Test::WWW::Mechanize for Catalyst
|
Description :
Catalyst is an elegant MVC Web Application Framework. Test::WWW::Mechanize
is a subclass of WWW::Mechanize that incorporates features for web
application testing. The Test::WWW::Mechanize::Catalyst module meshes the
two to allow easy testing of Catalyst applications without needing to start
up a web server.
Testing web applications has always been a bit tricky, normally requiring
starting a web server for your application and making real HTTP requests to
it. This module allows you to test Catalyst web applications but does not
require a server or issue HTTP requests. Instead, it passes the HTTP
request object directly to Catalyst. Thus you do not need to use a real
hostname: \"http://localhost/\" will do. However, this is optional. The
following two lines of code do exactly the same thing:
$mech->get_ok(\'/action\');
$mech->get_ok(\'http://localhost/action\');
Links which do not begin with / or are not for localhost can be handled as
normal Web requests - this is handy if you have an external single sign-on
system. You must set allow_external to true for this:
$mech->allow_external(1);
You can also test a remote server by setting the environment variable
CATALYST_SERVER; for example:
$ CATALYST_SERVER=http://example.com/myapp prove -l t
will run the same tests on the application running at
http://example.com/myapp regardless of whether or not you specify
http:://localhost for Test::WWW::Mechanize::Catalyst.
Furthermore, if you set CATALYST_SERVER, the server will be regarded as a
remote server even if your links point to localhost. Thus, you can use
Test::WWW::Mechanize::Catalyst to test your live webserver running on your
local machine, if you need to test aspects of your deployment environment
(for example, configuration options in an http.conf file) instead of just
the Catalyst request handling.
This makes testing fast and easy. Test::WWW::Mechanize provides 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\" );
This module supports cookies automatically.
To use this module you must pass it the name of the application. See the
SYNOPSIS above.
Note that Catalyst has a special development feature: the debug screen. By
default this module will treat responses which are the debug screen as
failures. If you actually want to test debug screens, please use:
$mech->{catalyst_debug} = 1;
An alternative to this module is Catalyst::Test.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/openSUSE_Tumbleweed/noarch |
