On Sun, 30 Sep 2001, Michael G Schwern wrote:
> OH! I thought you were literally using fork(), not running another
> program. Now that makes a little more sense.
Yeah, I realized I should've been clearer after a few exchanges (I'm
slow).
> I suppose the idea here is something like:
>
> system("some_test") for 1..3;
>
> so you test that you can run the same code simultaneously and they
> won't trip on each other?
Something like that. So I know what order the tests are in. I know how
many should be run each time. But when the 'some_test' code runs, it
shouldn't print a header (cause its in the middle of a larger batch) and
the analysis in the END{} block should be skipped cause its not really
done yet. But I _do_ want the Test::More functions. They're quite handy.
Actually, to make a testimonial. I just finished rewriting all the Alzabo
tests to use Test::More. In the process, I clarified the test suite,
added at least 100 or so new tests (mostly by breaking up old ones into
smaller units) and caught a few false positives. I think that a generic
ok() function makes it easier to have brain farts in your tests. Having
to use a different function to test different things helped me find lots
of errors.
-dave
/*==================
www.urth.org
We await the New Sun
==================*/
