There's more than one way to do things | |
PerlMonks |
Testing, schmesting.by belden (Friar) |
on Sep 26, 2002 at 19:44 UTC ( [id://201019]=note: print w/replies, xml ) | Need Help?? |
Bah, testing. Who needs it? The list of reasons not to test is weighty:
Now, before reading such Meditations such as this one, or chromatic's testing articles on perl.com, I *seriously* believed the above. (Well, partially believed some of it anyway.) If you learn quickly, you only need to make one mistake before taking up testing as part of your development process. I learn pretty slowly, though: it's taken me many mistakes, and even more meditations and articles than I care to link to. What changed my mind? I can't say. Experience, to be sure. However, experience just showed me that I needed to do something different - not what I should be doing different, or how. Monks - if you found yourself agreeing with my list above - re-read Ovid's node. Re-read Zaxo's reply. Dissect trs80's sample testing code. Super Search for nodes that talk about testing. You can afford to be picky in authorship: everyone who's anyone has written about the benefits of testing somewhere within the Monastery. And give testing a shot. Through the Monastery I've become aware of the importance of good coding practices: use strict; use warnings; profile before optimizing; seek thee a better algorithm; test, test, and test again.
blyman
In Section
Meditations
|
|