Hi Geoff, Thanks for the info and the patch. I applied the patch without a problem and then went to install the developer release of T::M. Dost my eyes decieve me or does that say it was last updated on November 11, 2002? That's a long release cycle.
At any rate, I installed the latest copy of T::M and read your directions in the patch. However, I'm still not getting the expected results. I suppose that could be the fuzz factor you mentioned but put together a new version of my test package in case you want to see if I'm just doing something stupid[1]. I understand that you can't release this code until T::M is released but considering that T::M may be a bit longer baking, an additional caveat in the A::T pod would be useful in case T::M doesn't get released before the next release of A::T. I've attached a patch against the pristine version of 1.12. Thanks, William [1] http://knowmad.com/~william/testmore-bug.tar.gz -- Knowmad Services Inc. http://www.knowmad.com
--- Test.pm.orig 2004-06-24 09:18:31.000000000 -0400 +++ Test.pm.wlm 2004-07-10 12:39:47.000000000 -0400 @@ -763,7 +763,7 @@ =head1 Test::More Integration There are a few caveats if you want to use I<Apache::Test> with -I<Test::More> instead of the default I<Test> backend. The first is +I<Test::More> instead of the default I<Test> backend. The first is that you cannot use it in response tests (yet). The second is that I<Test::More> requires you to use its own C<plan()> function and not the one that ships with I<Apache::Test>. I<Test::More> also defines C<ok()> and C<skip()> functions that are different, and
