You are viewing a plain text version of this content. The canonical link for it is here.
Posted to test-dev@httpd.apache.org by Geoffrey Young <ge...@modperlcookbook.org> on 2004/07/15 02:15:13 UTC
Re: cvs commit: httpd-test/perl-framework/Apache-Test/lib/Apache
TestConfig.pm TestConfigPerl.pm
> +If a directory t/lib exists from where the tests are run, adjust
> +@INC so that this directory is added when running the tests,
> +both within t/TEST and within t/conf/modperl_inc.pl.
> +This allows inclusion of modules specific to the tests that
> +aren't intended to be installed. [Stas, Randy]
for the record, you could always do this - I stick my test-specific modules
right in t/, such as t/My/Handler.pm.
but I guess it makes sense to have them all under a common t/lib so that t/
isn't sprinkled with a dozen different namespaces. so +1 after the fact ;)
--Geoff
Re: cvs commit: httpd-test/perl-framework/Apache-Test/lib/Apache
TestConfig.pm TestConfigPerl.pm
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>
>>And may be this is a good idea for the A-T skeleton as well :)
>
>
> indeed :)
>
> actually, the bug reporting skeleton used t/My/Handler.pm, and I'll
> certainly change that to t/lib not.
ECANTPARSETHAT
> the A-T module skeleton actually starts
> with no supporting modules, since you would want to install the module
> you're testing. but maybe I'll come up with something anyway :)
:)
--
__________________________________________________________________
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
Re: cvs commit: httpd-test/perl-framework/Apache-Test/lib/Apache
TestConfig.pm TestConfigPerl.pm
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
> And may be this is a good idea for the A-T skeleton as well :)
indeed :)
actually, the bug reporting skeleton used t/My/Handler.pm, and I'll
certainly change that to t/lib not. the A-T module skeleton actually starts
with no supporting modules, since you would want to install the module
you're testing. but maybe I'll come up with something anyway :)
--Geoff
Re: cvs commit: httpd-test/perl-framework/Apache-Test/lib/Apache
TestConfig.pm TestConfigPerl.pm
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>> +If a directory t/lib exists from where the tests are run, adjust
>> +@INC so that this directory is added when running the tests,
>> +both within t/TEST and within t/conf/modperl_inc.pl.
>> +This allows inclusion of modules specific to the tests that
>> +aren't intended to be installed. [Stas, Randy]
>
>
> for the record, you could always do this - I stick my test-specific modules
> right in t/, such as t/My/Handler.pm.
>
> but I guess it makes sense to have them all under a common t/lib so that t/
> isn't sprinkled with a dozen different namespaces. so +1 after the fact ;)
And may be this is a good idea for the A-T skeleton as well :)
--
__________________________________________________________________
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