use Perl

• Red Apples vs Green Apples (Score:2)

  by djberg96 (2603)

  Hey, never let facts get in the way of a little hyperbole. ;)

  Perl has had a canonical test suite in the core repository and shipped those tests with every source distribution since 1987. As of at least Ruby 1.8.7 (May 2008), this was not true of Ruby.

  I wouldn't equate a core development team with that language's community. The Perl core team certainly was and is fanatical about testing, but the community? I think they caught up much later. In the case of Ruby we have the opposite situation - the community
  • Re: (Score:1)

    by chromatic (983)

    The Perl core team certainly was and is fanatical about testing, but the community? I think they caught up much later.

    In 2000, CPAN authors had the expectation to write tests. The CPAN client ran those tests when installing modules.

    It's 2009. Does Ruby gems run tests yet?

    Adding features is usually a simple matter of subclassing (with Test::Unit anyway - I don't use RSpec).

    You don't even have to do this with Perl. Someone writes a new test module, once, uploads it to the CPAN, and then everyone can us
    • Re:Red Apples vs Green Apples (Score:2)

      by djberg96 (2603) on 2009.02.16 19:44 (#67421) Journal

      In 2000, CPAN authors had the expectation to write tests. The CPAN client ran those tests when installing modules.

      Yeah, but I don't know when a real jump was made from running that stock one-test default test file that h2xs generated to people being really good about writing tests. That's hard to know for sure, but I would put it somewhere around 2002. But still, yeah, pretty good.

      You don't even have to do this with Perl. Someone writes a new test module, once, uploads it to the CPAN, and then everyone can use it without subclassing or trying to get multiple subclasses to work together nicely.

      Actually, I misspoke. With open classes you don't need to subclass, so just require'ing the library is good enough. That's what the context, matchy and stump libraries all do as far as I know.

      It's 2009. Does Ruby gems run tests yet?

      It's always been possible to my knowledge, it just doesn't run them by default. I think the decision to not run them by default is, in part, because of the weakness of Test::Unit 1.x.

      Reply to This

      Parent

      • Re: (Score:1)

        by chromatic (983)

        That's hard to know for sure, but I would put it somewhere around 2002.

        It started in late 2001, but you're probably right that it only became popular and inevitable in 2002. I spent a lot of time in late 2001 avoiding finishing a book and writing tests for the Perl 5 core instead.

        I think the decision to not run them by default is, in part, because of the weakness of Test::Unit 1.x.

        That's what I don't get about the "Rah rah, TDD whee!" cheerleading from some parts of the Ruby community. You might as we
        • Re: (Score:1)

          by Arador (8415)

          That's what I don't get about the "Rah rah, TDD whee!" cheerleading from some parts of the Ruby community. You might as well not write tests if you're not going to run them.

          Yeah, that makes no sense to me either.