Lately my downfall has been buggy test scripts.
- Wrong test count. I know there's a no_plan option, but that would leave me defenseless against
- Premature death of test script. Often the result of trying to exercise exceptions and error handlers. Yes, I know, the remedy is eval.
- Remembering how to use TODO and skip and skip_todo, or is that todo_skip? Finding out that skip if doesn't always protect a test script from tests that blow up, even though they're supposed to be skipped. See previous point.
- Testing exec.
- Forgetting to use diag for output, and printing something in a format that confuses the test harness.
- Testing subroutines and methods that print their own output.
It's still worth writing tests. Once I get a test to work, I can keep it around forever, and regression testing has saved me a lot of time over the years. I just wish there were a Test::Test module.
-
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.
|
