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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • turning Perl into the most testable platform on the planet

    This is an excellent point. I wonder if anyone has used Perl's new improved testing features to persuade their bosses to use Perl over some other language.

    How do other languages stack up against Perl in testability?

    • Ruby's Test::Unit [talbott.ws] (by Nathanial Talbott) works well. I haven't used either one very extensively, but I think they're about on par with each other. I've used it to help me catch some bugs while porting Spreadsheet::WriteExcel.

      Someone feel free to disagree...

      • by Matts (1087) on 2002.12.11 16:35 (#15346) Journal
        I don't want to disagree, but I still think Ruby has a long way to go in this respect. It still has no unified build framework (unless this has changed recently), and since it doesn't have the above, I'm assuming it doesn't have a unified test harness framework.

        While ruby's Test::Unit looks vaguely interesting, it doesn't look nearly as simple as Test::Harness + Test.pm (or Test::More). The thing about Test::Harness is that it's not a module, but a tool. And a nice tool at that - it shows me test progress, and when I get test errors it shows them as I'm progressing, so that if I want to I can ctrl-C the tests and fix them.

        I don't know for sure if the ruby stuff doesn't provide this, so I could be blowing bubbles here. Please correct me if I'm wrong.

        I guess I just want CPAN for ruby. Once that's there, all this stuff kind of happens as a consequence of that.