Standard Unit Testing Framework?

Along these same lines, is there any chance of automatically adding targets
for mkmf the way Perl’s ExtUtils::MakeMaker module does? It uses
Test::Harness and runs the file “test.pl” and/or looks for test files by
globbing “t/*.t” (i.e. any file in the ‘t’ directory that ends with ‘.t’).

What do you think?

Regards,

Dan

···

-----Original Message-----
From: matz@ruby-lang.org [mailto:matz@ruby-lang.org]
Hi,

In message “Standard Unit Testing Framework?” > on 02/08/08, Lyle Johnson lyle@users.sourceforge.net writes:

Was a decision ever made about incorporating one of the unit testing
frameworks (either RubyUnit or Test::Unit) into the Ruby 1.7
distribution? I don’t mean as an add-on package, but a
standard part of
the library. It seemed at one point that Test::Unit had been
declared
the heir apparent to RubyUnit (see e.g. ruby-talk:23904),
and I thought
I saw posts that indicated that it was being incorporated
into the Ruby
standard library.

Test::Unit will. But I don’t follow the situation between their
authors.

  					matz.

Hi,

···

In message “RE: Standard Unit Testing Framework?” on 02/08/09, “Berger, Daniel” djberge@qwest.com writes:

Along these same lines, is there any chance of automatically adding targets
for mkmf the way Perl’s ExtUtils::MakeMaker module does? It uses
Test::Harness and runs the file “test.pl” and/or looks for test files by
globbing “t/*.t” (i.e. any file in the ‘t’ directory that ends with ‘.t’).

What do you think?

Once we adopt Test::Unit in the distribution.

						matz.