Probably this is obvious to all, but this is going about the wrong way round (not that you can help it, mind). The Right Way to Do It(tm) is to first write the test, then the code it's supposed to test. At least if you buy into the extreme programming philosophy and unit testing approach.
It's better to develop tests and code in that order since at the point you write the test, it's still a black box, and you're forced to think ahead of border and corner cases. In a way, the developer is more open-minded towards his own work before he's done it than afterwards.
Again, it doesn't apply to your particular situation, but it's something that might be worth keeping in mind for future projects. And yes, it's all in the books mentioneed above, but I like to stress it nevertheless ;-)
And again, yes, I do program that way and enjoy it a lot.
Just my 2 cents, -gjb-
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||