mod_perl is hard to test because you have to test how your code interacts with the black box that is Apache's guts; how it copes with running lots of copies concurrently; and so on. Yes, it's easier if your code is in nice little modules that are decoupled from mod_perl, but then you're not testing mod_perl. You still need to test to thin layer that sits between your modules and mod_perl and you still need to test the concurrency bit. Programmers aren't used to thinking about concurrency even if they jolly well should be, as can be seen from the vast majority of code on the CPAN which doesn't bother with any concurrent tests at all, let alone really carefully testing it.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||