Commit | Line | Data |
d442cc9f |
1 | =head1 NAME |
2 | |
4b4d3884 |
3 | Catalyst::Manual::Tutorial::Testing - Catalyst Tutorial - Chapter 8: Testing |
d442cc9f |
4 | |
5 | |
6 | =head1 OVERVIEW |
7 | |
4b4d3884 |
8 | This is B<Chapter 8 of 10> for the Catalyst tutorial. |
d442cc9f |
9 | |
10 | L<Tutorial Overview|Catalyst::Manual::Tutorial> |
11 | |
12 | =over 4 |
13 | |
14 | =item 1 |
15 | |
16 | L<Introduction|Catalyst::Manual::Tutorial::Intro> |
17 | |
18 | =item 2 |
19 | |
20 | L<Catalyst Basics|Catalyst::Manual::Tutorial::CatalystBasics> |
21 | |
22 | =item 3 |
23 | |
3533daff |
24 | L<More Catalyst Basics|Catalyst::Manual::Tutorial::MoreCatalystBasics> |
d442cc9f |
25 | |
26 | =item 4 |
27 | |
3533daff |
28 | L<Basic CRUD|Catalyst::Manual::Tutorial::BasicCRUD> |
d442cc9f |
29 | |
30 | =item 5 |
31 | |
3533daff |
32 | L<Authentication|Catalyst::Manual::Tutorial::Authentication> |
d442cc9f |
33 | |
34 | =item 6 |
35 | |
3533daff |
36 | L<Authorization|Catalyst::Manual::Tutorial::Authorization> |
d442cc9f |
37 | |
38 | =item 7 |
39 | |
3533daff |
40 | L<Debugging|Catalyst::Manual::Tutorial::Debugging> |
d442cc9f |
41 | |
42 | =item 8 |
43 | |
3533daff |
44 | B<Testing> |
d442cc9f |
45 | |
46 | =item 9 |
47 | |
3533daff |
48 | L<Advanced CRUD|Catalyst::Manual::Tutorial::AdvancedCRUD> |
49 | |
50 | =item 10 |
51 | |
d442cc9f |
52 | L<Appendices|Catalyst::Manual::Tutorial::Appendices> |
53 | |
54 | =back |
55 | |
3533daff |
56 | |
d442cc9f |
57 | =head1 DESCRIPTION |
58 | |
4b4d3884 |
59 | You may have noticed that the Catalyst Helper scripts automatically |
60 | create basic C<.t> test scripts under the C<t> directory. This |
61 | chapter of the tutorial briefly looks at how these tests can be used |
62 | to not only ensure that your application is working correctly at the |
63 | present time, but also provide automated regression testing as you |
64 | upgrade various pieces of your application over time. |
d442cc9f |
65 | |
4d63a0d5 |
66 | You can check out the source code for this example from the Catalyst |
67 | Subversion repository as per the instructions in |
1390ef0e |
68 | L<Catalyst::Manual::Tutorial::Intro|Catalyst::Manual::Tutorial::Intro>. |
69 | |
d442cc9f |
70 | |
71 | =head1 RUNNING THE "CANNED" CATALYST TESTS |
72 | |
73 | There are a variety of ways to run Catalyst and Perl tests (for example, |
74 | C<perl Makefile.PL> and C<make test>), but one of the easiest is with the |
75 | C<prove> command. For example, to run all of the tests in the C<t> |
76 | directory, enter: |
77 | |
78 | $ prove --lib lib t |
79 | |
028b4e1a |
80 | There will be a lot of output because we have the C<-Debug> flag |
81 | enabled in C<lib/MyApp.pm> (see the C<CATALYST_DEBUG=0> tip below for |
82 | a quick and easy way to reduce the clutter). Look for lines like this |
83 | for errors: |
3533daff |
84 | |
85 | # Failed test 'Request should succeed' |
86 | # in t/controller_Books.t at line 8. |
87 | # Looks like you failed 1 test of 3. |
88 | |
89 | The redirection used by the Authentication plugins will cause several |
90 | failures in the default tests. You can fix this by making the following |
91 | changes: |
92 | |
acbd7bdd |
93 | 1) Change the line in C<t/01app.t> that reads: |
d442cc9f |
94 | |
95 | ok( request('/')->is_success, 'Request should succeed' ); |
96 | |
97 | to: |
98 | |
99 | ok( request('/login')->is_success, 'Request should succeed' ); |
100 | |
fbbb9084 |
101 | 2) Change the "C<request('/logout')-E<gt>is_success>" to |
102 | "C<request('/logout')-E<gt>is_redirect>" in C<t/controller_Logout.t>. |
d442cc9f |
103 | |
fbbb9084 |
104 | 3) Change the "C<request('/books')-E<gt>is_success>" to |
105 | "C<request('/books')-E<gt>is_redirect>" in C<t/controller_Books.t>. |
d442cc9f |
106 | |
fbbb9084 |
107 | 4) Add "C<use MyApp;>" to the top of C<t/view_TT.t>. |
6a72d1bf |
108 | |
d442cc9f |
109 | As you can see in the C<prove> command line above, the C<--lib> option |
110 | is used to set the location of the Catalyst C<lib> directory. With this |
111 | command, you will get all of the usual development server debug output, |
112 | something most people prefer to disable while running tests cases. |
113 | Although you can edit the C<lib/MyApp.pm> to comment out the C<-Debug> |
114 | plugin, it's generally easier to simply set the C<CATALYST_DEBUG=0> |
115 | environment variable. For example: |
116 | |
117 | $ CATALYST_DEBUG=0 prove --lib lib t |
118 | |
119 | During the C<t/02pod> and C<t/03podcoverage> tests, you might notice the |
120 | C<all skipped: set TEST_POD to enable this test> warning message. To |
121 | execute the Pod-related tests, add C<TEST_POD=1> to the C<prove> |
122 | command: |
123 | |
124 | $ CATALYST_DEBUG=0 TEST_POD=1 prove --lib lib t |
125 | |
126 | If you omitted the Pod comments from any of the methods that were |
127 | inserted, you might have to go back and fix them to get these tests to |
128 | pass. :-) |
129 | |
130 | Another useful option is the C<verbose> (C<-v>) option to C<prove>. It |
131 | prints the name of each test case as it is being run: |
132 | |
133 | $ CATALYST_DEBUG=0 TEST_POD=1 prove --lib lib -v t |
134 | |
3533daff |
135 | |
d442cc9f |
136 | =head1 RUNNING A SINGLE TEST |
137 | |
138 | You can also run a single script by appending its name to the C<prove> |
139 | command. For example: |
140 | |
141 | $ CATALYST_DEBUG=0 prove --lib lib t/01app.t |
142 | |
3533daff |
143 | Also note that you can also run tests directly from Perl without C<prove>. |
d442cc9f |
144 | For example: |
145 | |
146 | $ CATALYST_DEBUG=0 perl -Ilib t/01app.t |
147 | |
3533daff |
148 | |
d442cc9f |
149 | =head1 ADDING YOUR OWN TEST SCRIPT |
150 | |
151 | Although the Catalyst helper scripts provide a basic level of checks |
152 | "for free," testing can become significantly more helpful when you write |
153 | your own script to exercise the various parts of your application. The |
154 | L<Test::WWW::Mechanize::Catalyst|Test::WWW::Mechanize::Catalyst> module |
155 | is very popular for writing these sorts of test cases. This module |
156 | extends L<Test::WWW::Mechanize|Test::WWW::Mechanize> (and therefore |
157 | L<WWW::Mechanize|WWW::Mechanize>) to allow you to automate the action of |
158 | a user "clicking around" inside your application. It gives you all the |
159 | benefits of testing on a live system without the messiness of having to |
160 | use an actual web server, and a real person to do the clicking. |
161 | |
162 | To create a sample test case, open the C<t/live_app01.t> file in your |
163 | editor and enter the following: |
164 | |
165 | #!/usr/bin/perl |
166 | |
167 | use strict; |
168 | use warnings; |
169 | |
170 | # Load testing framework and use 'no_plan' to dynamically pick up |
171 | # all tests. Better to replace "'no_plan'" with "tests => 30" so it |
172 | # knows exactly how many tests need to be run (and will tell you if |
173 | # not), but 'no_plan' is nice for quick & dirty tests |
174 | |
175 | use Test::More 'no_plan'; |
176 | |
177 | # Need to specify the name of your app as arg on next line |
178 | # Can also do: |
179 | # use Test::WWW::Mechanize::Catalyst "MyApp"; |
180 | |
181 | use ok "Test::WWW::Mechanize::Catalyst" => "MyApp"; |
182 | |
183 | # Create two 'user agents' to simulate two different users ('test01' & 'test02') |
184 | my $ua1 = Test::WWW::Mechanize::Catalyst->new; |
185 | my $ua2 = Test::WWW::Mechanize::Catalyst->new; |
186 | |
187 | # Use a simplified for loop to do tests that are common to both users |
188 | # Use get_ok() to make sure we can hit the base URL |
189 | # Second arg = optional description of test (will be displayed for failed tests) |
190 | # Note that in test scripts you send everything to 'http://localhost' |
191 | $_->get_ok("http://localhost/", "Check redirect of base URL") for $ua1, $ua2; |
192 | # Use title_is() to check the contents of the <title>...</title> tags |
193 | $_->title_is("Login", "Check for login title") for $ua1, $ua2; |
194 | # Use content_contains() to match on text in the html body |
195 | $_->content_contains("You need to log in to use this application", |
196 | "Check we are NOT logged in") for $ua1, $ua2; |
197 | |
198 | # Log in as each user |
199 | # Specify username and password on the URL |
200 | $ua1->get_ok("http://localhost/login?username=test01&password=mypass", "Login 'test01'"); |
201 | # Use the form for user 'test02'; note there is no description here |
202 | $ua2->submit_form( |
203 | fields => { |
204 | username => 'test02', |
205 | password => 'mypass', |
206 | }); |
207 | |
208 | # Go back to the login page and it should show that we are already logged in |
209 | $_->get_ok("http://localhost/login", "Return to '/login'") for $ua1, $ua2; |
210 | $_->title_is("Login", "Check for login page") for $ua1, $ua2; |
211 | $_->content_contains("Please Note: You are already logged in as ", |
212 | "Check we ARE logged in" ) for $ua1, $ua2; |
213 | |
214 | # 'Click' the 'Logout' link (see also 'text_regex' and 'url_regex' options) |
028b4e1a |
215 | $_->follow_link_ok({n => 4}, "Logout via first link on page") for $ua1, $ua2; |
d442cc9f |
216 | $_->title_is("Login", "Check for login title") for $ua1, $ua2; |
217 | $_->content_contains("You need to log in to use this application", |
218 | "Check we are NOT logged in") for $ua1, $ua2; |
219 | |
220 | # Log back in |
221 | $ua1->get_ok("http://localhost/login?username=test01&password=mypass", "Login 'test01'"); |
222 | $ua2->get_ok("http://localhost/login?username=test02&password=mypass", "Login 'test02'"); |
223 | # Should be at the Book List page... do some checks to confirm |
224 | $_->title_is("Book List", "Check for book list title") for $ua1, $ua2; |
225 | |
226 | $ua1->get_ok("http://localhost/books/list", "'test01' book list"); |
227 | $ua1->get_ok("http://localhost/login", "Login Page"); |
228 | $ua1->get_ok("http://localhost/books/list", "'test01' book list"); |
229 | |
230 | $_->content_contains("Book List", "Check for book list title") for $ua1, $ua2; |
231 | # Make sure the appropriate logout buttons are displayed |
fbbb9084 |
232 | $_->content_contains("/logout\">User Logout</a>", |
d442cc9f |
233 | "Both users should have a 'User Logout'") for $ua1, $ua2; |
234 | $ua1->content_contains("/books/form_create\">Create</a>", |
235 | "Only 'test01' should have a create link"); |
236 | |
237 | $ua1->get_ok("http://localhost/books/list", "View book list as 'test01'"); |
238 | |
239 | # User 'test01' should be able to create a book with the "formless create" URL |
240 | $ua1->get_ok("http://localhost/books/url_create/TestTitle/2/4", |
241 | "'test01' formless create"); |
242 | $ua1->title_is("Book Created", "Book created title"); |
243 | $ua1->content_contains("Added book 'TestTitle'", "Check title added OK"); |
244 | $ua1->content_contains("by 'Stevens'", "Check author added OK"); |
245 | $ua1->content_contains("with a rating of 2.", "Check rating added"); |
246 | # Try a regular expression to combine the previous 3 checks & account for whitespace |
247 | $ua1->content_like(qr/Added book 'TestTitle'\s+by 'Stevens'\s+with a rating of 2./, "Regex check"); |
248 | |
249 | # Make sure the new book shows in the list |
250 | $ua1->get_ok("http://localhost/books/list", "'test01' book list"); |
251 | $ua1->title_is("Book List", "Check logged in and at book list"); |
252 | $ua1->content_contains("Book List", "Book List page test"); |
253 | $ua1->content_contains("TestTitle", "Look for 'TestTitle'"); |
254 | |
255 | # Make sure the new book can be deleted |
256 | # Get all the Delete links on the list page |
257 | my @delLinks = $ua1->find_all_links(text => 'Delete'); |
258 | # Use the final link to delete the last book |
259 | $ua1->get_ok($delLinks[$#delLinks]->url, 'Delete last book'); |
260 | # Check that delete worked |
261 | $ua1->content_contains("Book List", "Book List page test"); |
262 | $ua1->content_contains("Book deleted", "Book was deleted"); |
263 | |
264 | # User 'test02' should not be able to add a book |
265 | $ua2->get_ok("http://localhost/books/url_create/TestTitle2/2/5", "'test02' add"); |
266 | $ua2->content_contains("Unauthorized!", "Check 'test02' cannot add"); |
267 | |
268 | The C<live_app.t> test cases uses copious comments to explain each step |
269 | of the process. In addition to the techniques shown here, there are a |
270 | variety of other methods available in |
271 | L<Test::WWW::Mechanize::Catalyst|Test::WWW::Mechanize::Catalyst> (for |
272 | example, regex-based matching). Consult the documentation for more |
273 | detail. |
274 | |
275 | B<TIP>: For I<unit tests> vs. the "full application tests" approach used |
276 | by L<Test::WWW::Mechanize::Catalyst|Test::WWW::Mechanize::Catalyst>, see |
277 | L<Catalyst::Test|Catalyst::Test>. |
278 | |
279 | B<Note:> The test script does not test the C<form_create> and |
280 | C<form_create_do> actions. That is left as an exercise for the reader |
281 | (you should be able to complete that logic using the existing code as a |
282 | template). |
283 | |
284 | To run the new test script, use a command such as: |
285 | |
286 | $ CATALYST_DEBUG=0 prove --lib lib -v t/live_app01.t |
287 | |
288 | or |
289 | |
290 | $ DBIC_TRACE=0 CATALYST_DEBUG=0 prove --lib lib -v t/live_app01.t |
291 | |
4b4d3884 |
292 | Experiment with the C<DBIC_TRACE>, C<CATALYST_DEBUG> and C<-v> |
293 | settings. If you find that there are errors, use the techniques |
294 | discussed in the "Catalyst Debugging" section (Chapter 7) to isolate |
295 | and fix any problems. |
d442cc9f |
296 | |
297 | If you want to run the test case under the Perl interactive debugger, |
298 | try a command such as: |
299 | |
300 | $ DBIC_TRACE=0 CATALYST_DEBUG=0 perl -d -Ilib t/live_app01.t |
301 | |
302 | Note that although this tutorial uses a single custom test case for |
303 | simplicity, you may wish to break your tests into different files for |
304 | better organization. |
305 | |
306 | B<TIP:> If you have a test case that fails, you will receive an error |
307 | similar to the following: |
308 | |
309 | # Failed test 'Check we are NOT logged in' |
310 | # in t/live_app01.t at line 31. |
311 | # searched: "\x{0a}<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Tran"... |
312 | # can't find: "You need to log in to use this application." |
313 | |
314 | Unfortunately, this only shows us the first 50 characters of the HTML |
315 | returned by the request -- not enough to determine where the problem |
316 | lies. A simple technique that can be used in such situations is to |
317 | temporarily insert a line similar to the following right after the |
318 | failed test: |
319 | |
6daaedc0 |
320 | diag $ua1->content; |
d442cc9f |
321 | |
322 | This will cause the full HTML returned by the request to be displayed. |
323 | |
fbbb9084 |
324 | Another approach to see the full HTML content at the failure point in |
325 | a series of tests would be to insert a "C<$DB::single=1;> right above |
326 | the location of the failure and run the test under the perl debugger |
327 | (with C<-d>) as shown above. Then you can use the debugger to explore |
328 | the state of the application right before or after the failure. |
329 | |
d442cc9f |
330 | |
331 | =head1 SUPPORTING BOTH PRODUCTION AND TEST DATABASES |
332 | |
333 | You may wish to leverage the techniques discussed in this tutorial to |
334 | maintain both a "production database" for your live application and a |
335 | "testing database" for your test cases. One advantage to |
336 | L<Test::WWW::Mechanize::Catalyst|Test::WWW::Mechanize::Catalyst> is that |
337 | it runs your full application; however, this can complicate things when |
338 | you want to support multiple databases. One solution is to allow the |
339 | database specification to be overridden with an environment variable. |
d0496197 |
340 | For example, open C<lib/MyApp/Model/DB.pm> in your editor and |
d442cc9f |
341 | change the C<__PACKAGE__-E<gt>config(...> declaration to resemble: |
342 | |
343 | my $dsn = $ENV{MYAPP_DSN} ||= 'dbi:SQLite:myapp.db'; |
344 | __PACKAGE__->config( |
d0496197 |
345 | schema_class => 'MyApp::Schema', |
d442cc9f |
346 | connect_info => [ |
347 | $dsn, |
d442cc9f |
348 | ], |
349 | ); |
350 | |
351 | Then, when you run your test case, you can use commands such as: |
352 | |
353 | $ cp myapp.db myappTEST.db |
354 | $ CATALYST_DEBUG=0 MYAPP_DSN="dbi:SQLite:myappTEST.db" prove --lib lib -v t/live_app01.t |
355 | |
356 | This will modify the DSN only while the test case is running. If you |
357 | launch your normal application without the C<MYAPP_DSN> environment |
358 | variable defined, it will default to the same C<dbi:SQLite:myapp.db> as |
359 | before. |
360 | |
361 | |
362 | =head1 AUTHOR |
363 | |
364 | Kennedy Clark, C<hkclark@gmail.com> |
365 | |
366 | Please report any errors, issues or suggestions to the author. The |
367 | most recent version of the Catalyst Tutorial can be found at |
82ab4bbf |
368 | L<http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Manual/5.70/trunk/lib/Catalyst/Manual/Tutorial/>. |
d442cc9f |
369 | |
45c7830f |
370 | Copyright 2006-2008, Kennedy Clark, under Creative Commons License |
8482d557 |
371 | (L<http://creativecommons.org/licenses/by-sa/3.0/us/>). |
d442cc9f |
372 | |