C<prove> command. For example, to run all of the tests in the C<t>
directory, enter:
- $ prove --lib lib t
+ $ prove -wl t
There will be a lot of output because we have the C<-Debug> flag
enabled in C<lib/MyApp.pm> (see the C<CATALYST_DEBUG=0> tip below for
plugin, it's generally easier to simply set the C<CATALYST_DEBUG=0>
environment variable. For example:
- $ CATALYST_DEBUG=0 prove --lib lib t
+ $ CATALYST_DEBUG=0 prove -wl t
B<Note:> Depending on the versions of various modules you have
installed, you might get some C<used only once> warnings -- you can
execute the Pod-related tests, add C<TEST_POD=1> to the C<prove>
command:
- $ CATALYST_DEBUG=0 TEST_POD=1 prove --lib lib t
+ $ CATALYST_DEBUG=0 TEST_POD=1 prove -wl t
If you omitted the Pod comments from any of the methods that were
inserted, you might have to go back and fix them to get these tests to
Another useful option is the C<verbose> (C<-v>) option to C<prove>. It
prints the name of each test case as it is being run:
- $ CATALYST_DEBUG=0 TEST_POD=1 prove --lib lib -v t
+ $ CATALYST_DEBUG=0 TEST_POD=1 prove -vwl t
=head1 RUNNING A SINGLE TEST
You can also run a single script by appending its name to the C<prove>
command. For example:
- $ CATALYST_DEBUG=0 prove --lib lib t/01app.t
+ $ CATALYST_DEBUG=0 prove -wl t/01app.t
Also note that you can also run tests directly from Perl without C<prove>.
For example:
- $ CATALYST_DEBUG=0 perl -Ilib t/01app.t
+ $ CATALYST_DEBUG=0 perl -w -Ilib t/01app.t
=head1 ADDING YOUR OWN TEST SCRIPT
use strict;
use warnings;
-
- # Load testing framework and use 'no_plan' to dynamically pick up
- # all tests. Better to replace "'no_plan'" with "tests => 30" so it
- # knows exactly how many tests need to be run (and will tell you if
- # not), but 'no_plan' is nice for quick & dirty tests
-
- use Test::More 'no_plan';
+ use Test::More;
# Need to specify the name of your app as arg on next line
# Can also do:
# Log in as each user
# Specify username and password on the URL
$ua1->get_ok("http://localhost/login?username=test01&password=mypass", "Login 'test01'");
- $ua1->get_ok("http://localhost/login?username=test02&password=mypass", "Login 'test02'");
+ # Could make user2 like user1 above, but use the form to show another way
+ $ua2->submit_form(
+ fields => {
+ username => 'test02',
+ password => 'mypass',
+ });
# Go back to the login page and it should show that we are already logged in
$_->get_ok("http://localhost/login", "Return to '/login'") for $ua1, $ua2;
# Make sure the appropriate logout buttons are displayed
$_->content_contains("/logout\">User Logout</a>",
"Both users should have a 'User Logout'") for $ua1, $ua2;
- $ua1->content_contains("/books/form_create\">Create</a>",
- "Only 'test01' should have a create link");
+ $ua1->content_contains("/books/form_create\">Admin Create</a>",
+ "'test01' should have a create link");
+ $ua2->content_lacks("/books/form_create\">Admin Create</a>",
+ "'test02' should NOT have a create link");
$ua1->get_ok("http://localhost/books/list", "View book list as 'test01'");
$ua2->get_ok("http://localhost/books/url_create/TestTitle2/2/5", "'test02' add");
$ua2->content_contains("Unauthorized!", "Check 'test02' cannot add");
+ done_testing;
+
The C<live_app.t> test cases uses copious comments to explain each step
of the process. In addition to the techniques shown here, there are a
variety of other methods available in
To run the new test script, use a command such as:
- $ CATALYST_DEBUG=0 prove --lib lib -v t/live_app01.t
+ $ CATALYST_DEBUG=0 prove -vwl t/live_app01.t
or
- $ DBIC_TRACE=0 CATALYST_DEBUG=0 prove --lib lib -v t/live_app01.t
+ $ DBIC_TRACE=0 CATALYST_DEBUG=0 prove -vwl t/live_app01.t
Experiment with the C<DBIC_TRACE>, C<CATALYST_DEBUG> and C<-v>
settings. If you find that there are errors, use the techniques
my $dsn = $ENV{MYAPP_DSN} ||= 'dbi:SQLite:myapp.db';
__PACKAGE__->config(
schema_class => 'MyApp::Schema',
- connect_info => [
- $dsn,
- ],
- );
+
+ connect_info => {
+ dsn => $dsn,
+ ...
Then, when you run your test case, you can use commands such as:
$ cp myapp.db myappTEST.db
- $ CATALYST_DEBUG=0 MYAPP_DSN="dbi:SQLite:myappTEST.db" prove --lib lib -v t/live_app01.t
+ $ CATALYST_DEBUG=0 MYAPP_DSN="dbi:SQLite:myappTEST.db" prove -vwl t/live_app01.t
This will modify the DSN only while the test case is running. If you
launch your normal application without the C<MYAPP_DSN> environment
Please report any errors, issues or suggestions to the author. The
most recent version of the Catalyst Tutorial can be found at
-L<http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Manual/5.70/trunk/lib/Catalyst/Manual/Tutorial/>.
+L<http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Manual/5.80/trunk/lib/Catalyst/Manual/Tutorial/>.
Copyright 2006-2008, Kennedy Clark, under Creative Commons License
(L<http://creativecommons.org/licenses/by-sa/3.0/us/>).