Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: domain of autarch@urth.org designates
 65.103.28.217 as permitted sender)
Date: Thu, 6 Jul 2006 09:23:42 -0500 (CDT)
From: Dave Rolsky <autarch@urth.org>
To: dev@perl.apache.org
Subject: Re: svn commit: r419247 - /perl/Apache-SizeLimit/trunk/Makefile.PL
In-Reply-To: <44AD1A15.4090107@modperlcookbook.org>
Message-ID: <Pine.LNX.4.64.0607060918080.12328@urth.org>
References: <20060705150630.B30EC1A981A@eris.apache.org>
 <44AD0FD1.1050201@modperlcookbook.org>
 <Pine.LNX.4.64.0607060857500.12328@urth.org>
 <44AD1A15.4090107@modperlcookbook.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Thu, 6 Jul 2006, Geoffrey Young wrote:

>
>> 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});

It's too bad this isn't an Apache::Test method/function. That'd be quite 
handy.

> 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.

Unfortunately it doesn't, which is kind of bad, since I have 
TestConfigData.pm and it's kind of important that I can run the tests. 
That may be why I first looked at that code and wanted to remove it.

> "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?

I'm with you on the goal, but I think it needs to check to for 
TestConfigData.pm and ~/.apache-test as well to be useful.

Is there a separate check I can do for those? Looking at 
Apache::TestConfig I cannot figure out how to do it without invoking the 
prompts.


-dave

/*===================================================
VegGuide.Org                        www.BookIRead.com
Your guide to all that's veg.       My book blog
===================================================*/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org