You're being waaaaay too complicated, and you missed the point. The point behind all these practices has nothing to do with the initial product. It's all about managing change.
If you never had to change your program, does it really matter how well it's written? Do you really need the test suite? ... No, not really.
Here's a very simple way to get someone to understand the power of test suites:
- Grab a copy of CGI.pm off of CPAN
- Ask a coworker to add a small, but non-trivial, feature.
- If your coworker isn't Lincoln Stein, they will go goggle-eyed
- Offer the test suite and ask them if having it makes them feel better about making the change.
- Don't say another word.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
-
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.
|
