I came up with a strategy for this type of thing working on a project that uses
CGI::Application and
Template. First, unlike the usual CGI::App style, my runmodes return only raw data structures and I save the template rendering for the
cgiapp_postrun phase. When running tests, I can override the
cgiapp_postun method and set
$ENV{CGI_APP_RETURN_ONLY} = 1. Then I can set up a fake CGI environment, load and run my module directly (without going through a web server) and use stuff like
is_deeply to make sure the data structure looks right.
I also have a separate set of tests for making sure the templates render properly.
Also, since my app has a rather large inherritence tree and lots of small subclasses that only override a method or two, I use Test::Class to do xUnit style inherrited tests. That way I can set up a new subclass that might only have a dozen lines of code, and set up its test class to inherrit the six hundred tests from the parent class.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.