On Wed, Jan 14, 2004 at 08:41:01PM -0800, Stas Bekman wrote:
> Cool, now I get the thing running.
Great. Are you getting any failures? Please read my notes in
testnotes.txt.
> What is this diff? Should I apply it
> against [1]? Why not just update your snapshot?
Sorry, this is against the testing docs[1]. I've attached a diff -u. I
had to remove a couple sections that you added since I started my edits
so I may have messed things up. Hopefully you can see what I'm
suggesting.
William
[1] http://perl.apache.org/docs/general/testing/testing.html
--
Knowmad Services Inc.
http://www.knowmad.com
--- testing.pod.orig 2004-01-14 22:15:37.000000000 -0500
+++ testing.pod 2004-01-14 21:16:30.000000000 -0500
@@ -361,7 +358,7 @@
in order to try to detect as many problems as possible during the
testing process, it's may be useful to run tests in different orders.
-This if of course mosly useful in conjunction with I<-times=N> option.
+This is of course mostly useful in conjunction with I<-times=N> option.
Assuming that we have tests a, b and c:
@@ -900,10 +897,13 @@
#-------------------------
# this file will be Include-d by @ServerRoot@/httpd.conf
- # where Apache::Amazing can be found
- PerlSwitches [EMAIL PROTECTED]@/../lib
- # preload the module
- PerlModule Apache::Amazing
+ <IfDefine MODPERL2>
+ # This section is not necessary but can provide better performance
+ # where Apache::Amazing can be found
+ PerlSwitches [EMAIL PROTECTED]@/../lib
+ # preload the module
+ PerlModule Apache::Amazing
+ </IfDefine>
<Location /test/amazing>
SetHandler modperl
PerlResponseHandler Apache::Amazing
@@ -2383,7 +2383,7 @@
# received: a bad value
not ok 1
-we can see exactly what's the problem, by visual expecting of the
+we can see exactly what's the problem, by visual examinination of the
expected and received values.
It's true that adding a few print statements for each sub tests is
