On Mon, Jul 18, 2005 at 09:42:06AM -0400, Brett Sanger ([EMAIL PROTECTED]) wrote: > Currently I have a directory tree, and my testing consists of running > prove on one .t file, a directory, or recursively over all. I don't > seem to have a means of controlling the order of tests without using the > shell. (i.e. "prove" will run the tests in whatever order it pleases. > "prove *" will run them in asciibetical order) Is that true?
prove runs in whatever order it gets them. > There are some tests that I would love to have abort as soon as they > fail. (If step 3 failed, then steps 4 and 5 are places I don't want to > go) Is there a way to make prove do this? I skimmed the > Test::Builder docs, in case I was going to have to roll my own > prove-like tool, and didn't see an obvious call there either. Test::Manifest is the way to get them in a certain order. > start of this email) or I have to copy the create and delete code into > each tests, making maintenance harder. Is there a common way to Or make a mini library of the common code. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
