Thanks in advance and hi,
The testing doc linked below mentions Apache::Test's handy ability to
autogenerate handler configuration sections to the httpd.conf that
Apache::Test generates.
The testing doc reads:
The configuration part for this test will be autogenerated
by the Apache::Test framework and added to the autogenerated
file t/conf/httpd.conf when make test or ./Build test or
t/TEST -configure is run. In our case the following
configuration section will be added:
<Location /TestApache__write>
SetHandler modperl
PerlResponseHandler TestApache::write
</Location>
http://perl.apache.org/docs/general/testing/testing.html#Developing_Response_only_Part_of_a_Test
In my instance, I'm creating both the handler module and the testing
module and would like Apache::Test to take care of the handler
configuration sections in httpd.conf for me.
Is this autogeneration courtesy limited to t/response directory?
I think the answer is yes as I can't seem to get Apache::Test to create
handlers for other modules that are not in t/response. But maybe I'm just
doing something simply silly.
If the autogeneration is NOT limited to the t/response directory, I'll
provide possibly silly details of what is not working for me.
In the mod perl test suite I find some examples of handler modules not in
the t/response directory that might have autogenerated httpd.conf
sections.
For example t/filter/TestFilter/out_str_lc.pm
Which has in fact two handler directive for it in httpd.conf:
<Location /top_dir>
PerlOutputFilterHandler TestFilter::out_str_lc
</Location>
Alias /top_dir /home/jjm/src/mod_perl-1.99_17
<Location /TestFilter__out_str_lc>
PerlOutputFilterHandler TestFilter::out_str_lc
</Location>
Maybe some other magic puts those handler sections in httpd.conf.
I'm using apache 1.3.x and mod perl 1.17.
Just another Apache::Test wanna be,
Jim
