I'm on the edge of this whole unit test thing. It's not that unit tests are bad, they aren't, but for certain applications ... say systems monitoring and GUI apps (not always Perl), it's incredibly hard to write good unit tests. Small code (i.e. modules) can have unit tests pretty easily, large apps can be a challenge.
Furthermore, unit tests can help find problems, but fully successful unit tests can lead to false positives. You still can't test to see if your code will seg fault on RH QU 3 ... no matter what you do.
Meanwhile, if you are only unit testing your external API's, yes those API's shouldn't break when refactoring things. But if you are testing internal API's, well, it's ok to break those!
-
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.
|
