Here’s something interesting. This is the test directory from the very first version of Perl, released in 1987 and described by Larry as ‘a “replacement” for awk and sed’. Day one of Perl, and we already have the bare bones of the Test Anything Protocol and a prototype for Test::Harness in the TEST file.
If we truffle about in the various other branches we find other useful milestones for module developers:
- 5.000, in 1994 came with the first iteration of
h2xswhich could be used to generate the basic boilerplate for a perl module. Even today, with more sophisticated module starters available, you won’t find a CPAN module of repute that doesn’t follow the basic directory structure laid down in this utility.
ExtUtils::MakeMakergenerates a Makefile with a test target which runs all the tests in the
- 5.002, in 1996,
h2xsstarts stubbing test.pl
- 5.003_12, late 1996, first version of CPAN in the Perl distribution. From day one, CPAN would not install a module if any tests failed, unless you forced it.
- Has only recently embraced a language test suite
- Appears to have no standard layout for gem distributions
- Doesn’t run tests as part of the installation process for a new gem
Is it any wonder that chromatic gets a little cranky when sweeping claims are made about how spiffy Ruby’s testing culture is?
There are those who claim that CPAN is Perl’s shining glory, but it’s not really the collection of servers, it’s the toolchain that enables it, and that toolchain can exist because so many libraries follow a pretty minimal set of conventions.
I’d love to see the Ruby community settle on a similar, single, set of conventions for the way things should work. Start with a guarantee of a either a top level
install tasks. Make rubygems run the tests before installation, if the target is available, and halt the installation if they fail. Make it easy to send reports of test failures to module authors (look at the Perl CPAN and CPAN Testers sites, and their associated tooling for ideas).
I know… I should STFU And Write Some Code.
Further investigation shows that
gem install -t whatever does run the tests as part of the installation process. The capability is there, but it’s turned off by default. How depressing.