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.
  • I love Perl. I love testing :-)

    That said... while I see a lot of focus on *testing* in Perl. I've not encountered *that* much focus on TDD. They are - as you know - completely different things.

    Now I've not spent huge amount of time with Ruby teams / code bases / community - so I can't say whether they're better or worse. But evidence of testing != evidence of TDD.

    • TDD is all well and good, but if you don't run your tests, you've wasted your time writing them.

      Say what you like about the Perl community, the language, our testing libraries, our culture, or whatever -- but we run our tests.

      • TDD is all well and good, but if you don't run your tests, you've wasted your time writing them.

        No I haven't. I still get the "D" from TDD. I get that even if a third party never runs my tests again.

        I'm not saying running tests is useless. They're not. I'm not saying that the Perl/CPAN testing infrastructure isn't grand. It's fantastic - the best in any language that I've used.

        I'm just saying that it has nothing to do with whether Perl folk do TDD. Because it doesn't. And that was the quote you seemed to be responding to. And because folk misunderstanding and misinterpreting what TDD is often causes me a major PITA for me - I niggle :-)

        Whether the Ruby community is more obsessed with TDD than the Perl one - who knows...

        (As an aside, and in my experience, the Perl/CPAN infrastructure supports testing really well doesn't seem to have any relation to whether teams writing Perl code in the wild do good testing - TDD or not. That, like most development issues, is down to good people. No matter what language they use.)

        • As an aside, and in my experience, the Perl/CPAN infrastructure supports testing really well doesn't seem to have any relation to whether teams writing Perl code in the wild do good testing - TDD or not.

          Agreed, but we can measure that neither for Perl nor Ruby.

          Along those lines, I'm sure you have the same experience that I do, that many (if not most) people who claim to do TDD really don't, not in any pervasive fashion.

          Perhaps I've overspoken here, especially claiming that TDD without running the tests is