> -----Original Message-----
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 09, 2001 9:47 PM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: Apache::Test order
>
>
[snip]
>
> Also how about specifying the order in the Makefile.PL? I think Brian
> Moseley has asked for the same a few weeks ago and ended up using the
> Makefile.PL, see the earlier thread about ordering.
duh, don't know how I forgot about that - 'tis already been discussed :) my
brain is mush.
>
> Of course we can implement anything we need, but first I'm trying to
> understand the need ;)
>
it wasn't a need, really, but a preference - not the type of thing brian was
talking about.
even though all the tests are always run I thought it made sense to proceed
with them in a logical order, making them more informational. first load
module, them run a plain test, then run a complex test, etc...
for instance, I came up with the idea of checking for a sucessful filter via
my $content = ok GET_BODY '/handler';
ok ((GET_BODY '/filter'), "$content$content");
now, GET_BODY returns the body, regardless of error, while the next test
does not suceed unless the first is 200. thus the aggregate result is 1 ok,
2 not ok when really both tests failed.
I could use GET_OK before that, but what I'd like to do is GET_OK '/handler'
in its own test as to not repeat stuff. whether this test fails before or
after the filter test makes no difference, except that I think it makes more
sense to know the filter test is going to fail based on the fact that we
couldn't even get a plain test right...
as I said, just a preference, definitely not a need for me. maybe for
others, though...
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
