If you have any non-trivial SQL in your cdbi classes, I would test that against a predefined database (SQLite makes creating test databases easy). Any invariants of your non-stock constructors or set_sql queries fall under that.
I don't know what framework you already have for verifying/testing your created HTML, but I would go with something like Test::WWW::Mechanize or Test::HTML::Content (which really lacks functionality I admit) to see that the correct output gets created. This testing of the templates is more an end-to-end test though and not a test of the single snippets, but maybe you can create some stripped-down templates that leave out all the "uninteresting" fluff. Indeed, supplying an alternative configuration/template directory might be enough already for your different tests.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||