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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
