>
> So far as I can see, that is all directed at testing by sending a request
> to a server and checking what comes back; that's really not useful for
> testing components of code individually, which is the point. I don't
> want to test the server, I want to individually test each chunk of my code.
the kind of unit tests you are after are there as well. for instance, you
can plan tests within a handler
plan tests => 2, $r;
and do the typical
ok $foo->isa('bar');
type tests from within your handler. but yes, they all involve a running
server because most Apache/mod_perl things require a running server (like
access to $r). there's no easier way to unit-test mod_perl APIs than
Apache-Test - see the extensive mod_perl 2.0 test suite for examples.
HTH
--Geoff
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
