Stas Bekman wrote: [...]
But that's exactly what is happening. Test::Harness runs only only the client side, it actually runs the clients. Test::Harness in the A-T setup has no idea the server side exists at all. The server side can run ok/skip/etc via Test, Test::More, Apache::Test, etc. it then sends the output of these ok/skip/etc to the client as a normal response, which feeds it to Test::Harness.
You don't have to pass $r to plan() to get the server side tests working. It's just done for your convenience in the 'SetHandler modperl' mode, which wants you to do $r->print() and not print(). Since ok() will just print() the output won't go anywhere, since STDOUT is not tied/perlio'ed. So once you pass $r to plan() it just performs that trickery for you.
Oh and it also sets the content-type for you to 'text/plain'. and takes your kids to the kindergarden. oh, wait that latter feature is on the todo list.
__________________________________________________________________ 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
