# httpd-test-dev mailing list archives

##### Site index · List index
Message view
Top
From "William A. Rowe, Jr." <wr...@covalent.net>
Subject Re: [patch] hint why the test was skipped
Date Thu, 18 Oct 2001 12:54:48 GMT
From: "Stas Bekman" <stas@stason.org>
Sent: Wednesday, October 17, 2001 11:14 PM

> William A. Rowe, Jr. wrote:
>
> > From: "Stas Bekman" <stas@stason.org>
> > Sent: Wednesday, October 17, 2001 10:40 PM
> >
> >>  exec ./t/TEST protocol/eliza
> >>protocol/eliza....skipped: missing Chatbot::Eliza1
> >>All tests successful, 1 test skipped.
> >>
> >>The extension of Test::plan is already somewhat tricky, so in order to
> >>preserve the trick we have to make sure that our extension always
> >>returns a zero or one value. Since CODE and ARRAY refs were already
> >>taken I've used the available HASH ref. Now have module returns a reason
> >>for its failure, the CODE and ARRAY refs do or can do the same, here is
> >>how it works (this is incomplete, just to see if you like it):
> >>
> >
> > Without groking the code, definately +1 to allow Foo::try syntax, since we
> > on non-unix platforms already have problems with Foo/try vs Foo\try ;)
>
> Hmm, I guess you are talking about somethins else. What I try to do now
> is to print the reason for the skipped test.

That is, in and of itself, a great thing!

> Can you please expand on the problem you are talking about? And how do
> you want it to be handled?

Right now, we pass the argument to t/TEST somesuite/item.

If we adopted the Perl syntax of somesuite::item, the parsers wouldn't have
to deal with differences between somesuite/item.t and somesuite\item.t
which would make documenting the 'invoking' feature much simpler for all
platforms.

Right now, we generally worry about the 'unixish' family, and OS2, Win32
and Netware all accept foo/bar even though their native tounge is foo\bar.

If we ever support far stranger platforms [and you seem ready with all of
the file::spec code in the tree ;-] then this will become more difficult.


Mime
View raw message