running Apache::Test under Module::Build - not going to well

[Martyn Peck <mw...@mwpnet.com>]

Hello
(First off, I'm not sure this is the right list to talk about this, but 
I haven't been able to find a better one on my own. If there is a 
better list, Please let me know. Thanks.)

At work here we've decided to use Module::Build for all our mod_perl 
modules, and to use Apache::Test to test them with, And it's been my 
job to write the Apache::TestMB module that will get Apache::Test 
running under Module::Build. For the most part, I have been successful 
in this, and everything is running ok. Unfortunately, this has not been 
as straight forward or smooth as I would have hoped. Fist off is the 
fact that I was only able to get it working my having ./Build run the 
t/TEST script, which eliminates allot of the testing power of both 
Module::Build and Apache::Test.

More important than that, I've also run into a subtle but important 
incompatibility between the two. When running tests, Module::Build will 
always look in the current working directory for the configuration 
directory (normally _build/). But Apache::TestRun and 
Apache::TestHarness will change into the t/ directory to run the actual 
tests. Because of this Module::Build won't be able to find or load any 
of the configuration information. Unfortunately, I'm also setting up a 
test database to test against, and I need Module::Build to supply the 
connection information to each of the tests also. I got around this by 
subclassing both the new and current methods in our Apache::TestMB 
module, but I can already see how this is going to cause problems later 
on, for the other test modules I need to write.

So the big question is why is Apache::TestHarness changing into the t/ 
directory at all? I can see where some of the programming becomes 
easier by doing that. But overall I don't see what's gained by doing 
that.

Anyway, after spending the last two weeks going looking through code, 
I've basically come to the conclusion that to really get Apache::Test 
working under Module::Build (and not just the simple stop gap I'm 
using), will not only require a new module incorporating 
Apache::TestMM, Apache::TestRun and the t/TEST script, but will also 
require some major patches to Apache::TestHarness, and probably to 
Apaceh::TestConfig as well. Of course this is not something I can do on 
my own. But considering how important Module::Build is becoming, I'd 
think it would be a good idea to start talking about this.

Marty Peck


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

Re: running Apache::Test under Module::Build - not going to well

[Stas Bekman <st...@stason.org>]

Martyn Peck wrote:
> Hello
> (First off, I'm not sure this is the right list to talk about this, but 
> I haven't been able to find a better one on my own. If there is a better 
> list, Please let me know. Thanks.)

Martin, have you read Apache-Test/README?

###################
# Got a question? #
###################
Post it to the test-dev <at> httpd.apache.org list.
For more information see: http://httpd.apache.org/test/.


> At work here we've decided to use Module::Build for all our mod_perl 
> modules, and to use Apache::Test to test them with, And it's been my job 
> to write the Apache::TestMB module that will get Apache::Test running 
> under Module::Build. 

Great!
[...]
> So the big question is why is Apache::TestHarness changing into the t/ 
> directory at all? I can see where some of the programming becomes easier 
> by doing that. But overall I don't see what's gained by doing that.

It doesn't do that any longer. Check the current cvs (it will be released on 
CPAN in a few days).

> Anyway, after spending the last two weeks going looking through code, 
> I've basically come to the conclusion that to really get Apache::Test 
> working under Module::Build (and not just the simple stop gap I'm 
> using), will not only require a new module incorporating Apache::TestMM, 
> Apache::TestRun and the t/TEST script, but will also require some major 
> patches to Apache::TestHarness, and probably to Apaceh::TestConfig as 
> well. Of course this is not something I can do on my own. But 
> considering how important Module::Build is becoming, I'd think it would 
> be a good idea to start talking about this.

Absolutely. Please send patches with comments against the current cvs [1] to 
the test-dev mailing list.

[1]
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

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