No. But there are certain classes of functions of the module that don't work until others have been run. So others should have been tested rigorously in a previous test. For instance the first would be an error reporting function which should work no matter what (but I don't want to test it in every test file), then there are a class of functions for querying the system which only rely on error function that works, then there are establishing a template and using the template to set attributes, then there is job submission and synchronization, then there is job problem detection, then there is alternate job synchronization, then blah, blah...
But the tests get more complicated in progression so it will need to rely on previous tests having suceeded, OR write one giant test script. I just thought it would be more useful to the user to catch trivial problems in the first tests, and more complicated problems in later tests. However, Test::Manifest seems not to be a part of core perl, so if I used that it would be one more prereq module I'd need, so that is something of a draw back. ----- Original Message ----- From: "Andy Lester" <[EMAIL PROTECTED]> To: "Tim Harsch" <[EMAIL PROTECTED]> Cc: "Perl Mod Authors" <[EMAIL PROTECTED]> Sent: Friday, April 02, 2004 9:59 AM Subject: Re: running tests > > If I have several test files in my test suite, is there a way to get them to > > run in a predefined order when the user runs "make test"? I realize I could > > name them alphabetically like "Atest1.t, Bsometest.t", but it seems hokey > > and I'm not sure it would work on all systems. > > Also, WHY do you want them to run in a predefined order? Are you doing > setup in one, running some other tests, and then shutdown in another? > > xoa > > -- > Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
