On Sat, Jan 11, 2003 at 11:14:30PM +0000, Ed Avis wrote: > I thought the point of the .t files was that each was self-contained > and had its own setup and teardown. But I guess this is not a hard > and fast rule.
Hard and fast rules? In Perl?! Are you feeling ok? Most do have their own setup/teardown, but some, like MakeMaker, do rely on having a 00setup.t and a zz_cleanup.t. I've found it to be troublesome as it makes running an individual test more difficult than it should be, but it was easier to implement. Otherwise the need for ordering is more so you test the basic stuff first and the more complicated stuff later. Just so you don't have to plow through lots of failures only to find out its becuase one of your modules isn't compiling. > Hang on a minute - if this 01_setup.t test fails, surely every > following test will fail too? If you want to run 02_foo.t then you > must run 01_setup.t first. What is the point of having them as > separate test files, why not have a single test which runs all these > stages? Because long test programs are more difficult to maintain. > >So a new option in Makefile.PL like "MANIFEST_ORDERED_TESTS" => 1, > > If you want a particular ordering why not write a small Perl program > to call the files in the right order and make that the test case that > is run from 'make test'? As we all know, altering MakeMaker is Fraught With Peril. -- Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
