Randy Kobes wrote:
I've converted some more of the t/apr/ tests so as to test them under t/apr-ext/ - these are contained in the attached diff (which is quite large, hence I just attached it). This might be useful for testing for "hidden" mod_perl.so dependencies in the APR::* modules. One can use this neat feature of Apache-Test: perl t/TEST --no-httpd apr-ext to test these without starting Apache (thanks, Geoff!).
The tests in t/apr/ that aren't included here involve APR::Brigade, APR::OS, and APR::SockAddr.
I'm not sure that duplicating tests is a good idea. If we do so we will have to maintain two sets of mostly identical tests. I think that apr-ext could just test loading of the modules, a few basic tests (or none at all) and those features unique to APR, which aren't used under mod_perl (if there are such at all). So basically what I think we need is to just one test that loads all the modules. And a few more tests testing things like pool management. Thoughts?
I think it's possible to abstract the apr tests into self-contained units, independent of the client (not to rely on $r, and other apache parts). and then we could run each of those tests twice, once under mp2 and once more standalone. Though decoupling from $r may prove hard, since some tests use $r extensively internally.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
