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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Mac::Carbon and Testing 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ... did you find any bugs with your tests?

    --Nat

    • Re:Yes but ... (Score:1)

      by pudge (1) on 2002.11.07 12:03 (#14573) Homepage Journal
      Not that I can recall, but much of the test suite would have failed if not for detection of problems in my previous one-off tests (I wrote a lot of one-liners while working on the port).

      These modules have all been around so long (most of them for upwards of 6 years) that the bugs in them are few and far between. I am changing very little of the modules; most of the bugs will have to do with my ported support functions (for time conversions, GUSI replacement functions, etc.) and various unique interactions with Mac OS X.

      And at least one bug remains in the tests, though I can't really detect it with Perl (the Notification Manager simply doesn't play a sound I pass to it, and the only record of this is the fact that nothing comes out of the speakers ...).

      The test suite is just a beginning; it'd be nice to test every function in every conceivable way, but hopefully that is something other interested parties can help with. :D
      The most difficult modules to write tests for are Mac::Files and Mac::MoreFiles, and I imagine most bugs, if they exist, are to be found there. And those are the ones I've not yet written tests for.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.