I used to hate counting tests. Now I only dislike it mildly. The benefit of catching oopses has thus far outweighted the minor nuisance of keeping the numbers current. It's easy enough to run a .t by hand, quickly note how many tests it expects, note the number of the last test, and then edit the file to adjust the number. Two of my coworkers have an emacs macro that does this automagically.
One side-benefit of having explicit counts is that you can periodically traverse the code base to count tests (using File::Find or File::Find::Rule, and a regex), then chart the number over time.
-
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.
|
