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)

Sunday December 30, 2001
03:57 PM

To Hell With It

[ #1828 ]
Said of every good idea that can't play out before its time, I suspect.

I hoped (hoped!) that Test::Simple was included; it is not. I have the Activestate binary, and a few remarkably archaic discussions on Perlmonks have convinced me that testing is an animal I don't quite have the chops to tangle with yet.

Setting that aside for now, I move to *actually writing the friggin' script*. Lovely. At least I know a little more about modules and such; and found a few links to stuff about how to *make* modules.

Also, I saw Acme::Pony. I had honestly thought Acme::Buffy was the zenith of wacky, but...

Oh, and I *just* discovered COY! How amusing.

Damien wrote those
Coy and Acme:Bleach modules
They are hilarious

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 not so difficult [perl.com].

    Personally, I don't have the time not to test -- writing a Slash plugin for an article due next week, I'd have caught several bugs sooner if I'd written my test cases first. I caught them only after investing more debugging time than I would have liked.

    • I wasn't clear, and I apologize.

      First, I don't quite understand *when* testing needs to be done, where it happens, etc., like knowing basically what a transmission does but not realizing how it's actually applied within the mechanism of the whole car.

      Second, I am woefully bereft of any experience installing modules. (Although I'm going to the link you supply after I post this clarification to see if I can rectify the situation.)

      Believe me, when I *saw* the testing explained in the advent calendar, I

      --

      ------------------------------
      You are what you think.
      • Easily enough explained (and no apology is necessary).

        Test Continually. Test before you add a feature. Test when you think you've added that feature. Test after you make any change. Test when you return to the program in the morning. Test, test, test.

        If you test every feature sufficiently, if you refuse to accept anything less than complete test success, and if you run the tests after sufficiently small changes, you will have more confidence in your code, spend less time debugging, and be free to m