> I don't suppose there's a simple way to ask Apache::Test if it can find
> a server without prompting the user? That seems like the best way to
> test for this.
yeah, that's the code I had in there:
my %args = @Apache::TestMM::Argv;
die 'suitable httpd required'
unless ($args{apxs} or $args{httpd} or
$ENV{APACHE_TEST_HTTPD} or $ENV{APACHE_TEST_APXS});
basically, this checks standard Apache-Test %ENV variables as well as
cases like
$ perl Makefile.PL -apxs /usr/local/apache/bin/apxs
where the user is Apache-Test savvy. I _think_ it also covers when a
user has ~/.apache-test and/or TestConfigData.pm, but now I just can't
remember.
my goal for stuff like this has always been
"the tests will fail unless the httpd environment isn't properly set up,
but those test failures aren't really test failures they're environment
failures - you don't know if the tests fail or not because you can't
actually run them. so, do our best to set up the environment (without
prompting the user), but if we can't don't run the tests."
in my own modules, I really don't care about telling people "go setup
Apache-Test, then your tests won't fail" but for our public
distributions I think it looks bad to have failing cpan-tester reports
and bug reports flooding the dev list due to a bad test environment
(rather than actual failing tests).
make sense?
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
