Eimi Metamorphoumai has asked for the wisdom of the Perl Monks concerning the following question:
The details aren't that important, but what matters is that instead of being a collection of small subroutines that compute values (and can therefore be tested with all sorts of inputs to confirm that they produce the correct output), what I deal with are just big (but usually no more than a screenful or so of text) scripts that interact with the real world. I haven't come up with any automated testing proceedures, but putting one out there untested is very dangerous (when a couple thousand users lose their mail due to a bug, people become unhappy). So I'm doing ad hoc testing by running with the "payload" commented out, and multiple prints all over the place to show what it would be doing, and knowing in my gut that there has to be a better way. So I come seeking wisdom.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Test driven development and glue code
by InfiniteSilence (Curate) on Oct 05, 2005 at 14:50 UTC | |
Re: Test driven development and glue code
by xdg (Monsignor) on Oct 05, 2005 at 22:57 UTC | |
Re: Test driven development and glue code
by Perl Mouse (Chaplain) on Oct 05, 2005 at 14:54 UTC | |
Re: Test driven development and glue code
by eyepopslikeamosquito (Archbishop) on Oct 05, 2005 at 22:11 UTC |