On Sat, May 27, 2006 at 05:12:12PM +0200, Achim Grolms wrote:
> On Saturday 27 May 2006 16:15, Florian Ragwitz via RT wrote:
> > I'd suggest to either skip all tests that require networking unless some
> > condition is met, for example if $ENV{TEST_ONLINE} is set, or to be
> > smarter and try to detect if a network connection is available when
> > running the test suite.
>=20
> Skipping tests on some conditions is no problem,
> I can add that.
>=20
> But I dont't know *what* condition to test.
> Sure I can test if $ENV{TEST_ONLINE} is set, but who or what software
> sets that System-variable?
The user. Just like those pod and podcoverage test lots of people use
nowadays.
Those tests usually get skiped unless $ENV{TEST_POD} is set and the SKIP
message tells the user that, if he wants pod testing, he needs to set
that variable.
-Flo
--=20
BOFH excuse #392:
It's union rules. There's nothing we can do about it. Sorry.
|