Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chaoticset (2105)

chaoticset
  (email not shown publicly)
http://chaoticset.perlmonk.org/
AOL IM: chaoticset23 (Add Buddy, Send Message)
Yahoo! ID: illuminatus_foil (Add User, Send Message)

JAPH. (That's right -- I'm not Really Inexperienced any more.)

I'm not just here, I'm here [perlmonks.org], and here [javajunkies.org] too, I ramble randomly in my philosophical blog [blogspot.com] and my other blog [blogspot.com]. Soon I'll come in a convenient six-pack.

Journal of chaoticset (2105)

Saturday September 11, 2004
09:20 AM

Zen Of Testing

[ #20833 ]
A question on PM about code correction elicited the reply of "Rather than stealth code fixes, write good test cases that expose the bug."

Of course -- it's the time-honored process of a koan. A question is asked or a situation presented, where the error becomes obvious and enlightenment, if sought, is nearly unavoidable.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It's too bad that many people mis-intrepreted the point of that post. It wasn't so much about doing things without anyone else knowing (it mentions CVS, for instance), but not leaving multiple styles of coding in a source file.

    A lot of responders over-reacted, I think, because they hold onto some notion of code ownership or territoriality. That's not always the case when you have to work in a team and you might have to fix something yourself.

    Writing tests to motivate a bug fix is good, but not a rebutta