Write tests for your bugs before you fix the bugs. Check your test coverage with Devel::Cover before you refactor some code. If not all lines that are affected by your planned refactoring are covered, write tests. If you add new features, write tests before implementing the features. Don't waste time: don't write tests for mature code that you don't plan to change in the near future. It is no problem that you are late. The biggest problem is that your core API is probably not as clean as it should be for nice tests, simply because you did not need a clean API. Your test strategy depends on your existing code base. Maybe it is ok to refactor (modularize) your configuration code because it would not be too much work. But generally it is a bad idea to refactor mature code just to test it easier.
-
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.
|
