Like everything else in the world, it depends. If you need a specific environment which is non-standard, and needs to be set up properly to do tests, you may just need 1 test to ensure the data loads, and then provide examples of how to use the module. (It's amazing to me anyway how adjusting the documentation breaks things.) Otherwise, it's a good idea to write tests when a lot of people will be using the code. The only other gotcha I've come across is in emergency situations and you need an application 'now', then you may skip the testing to get the capability working, and then go back and ensure that you have valid tests for the code you wrote...
-
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.
|
