svn commit: r209503 - /perl/modperl/docs/trunk/src/docs/general/testing/testing.pod

[st...@apache.org]

Author: stas
Date: Wed Jul  6 12:34:56 2005
New Revision: 209503

URL: http://svn.apache.org/viewcvs?rev=209503&view=rev
Log:
s/C<Apache::Test> framework/C<Apache-Test> framework/, since the framework 
comprises more than one package

Modified:
    perl/modperl/docs/trunk/src/docs/general/testing/testing.pod

Modified: perl/modperl/docs/trunk/src/docs/general/testing/testing.pod
URL: http://svn.apache.org/viewcvs/perl/modperl/docs/trunk/src/docs/general/testing/testing.pod?rev=209503&r1=209502&r2=209503&view=diff
==============================================================================
--- perl/modperl/docs/trunk/src/docs/general/testing/testing.pod (original)
+++ perl/modperl/docs/trunk/src/docs/general/testing/testing.pod Wed Jul  6 12:34:56 2005
@@ -11,7 +11,7 @@
 mod_perl). Originally designed for the mod_perl Apache module, it was
 extended to be used for any Apache module.
 
-This chapter discusses the C<Apache::Test> framework, and in
+This chapter discusses the C<Apache-Test> framework, and in
 particular explains how to:
 
 =over
@@ -246,7 +246,7 @@
 
 =head2 Parallel Testing
 
-Sometimes you need to run more than one C<Apache::Test> framework
+Sometimes you need to run more than one C<Apache-Test> framework
 instances at the same time. In this case you have to use different
 ports for each instance. You can specify explicitly which port to use
 using the I<-port> configuration option. For example, to run the server
@@ -258,7 +258,7 @@
 evironment variable to the desired value before starting the server.
 
 Specifying the port explicitly may not be the most convenient option
-if you happen to run many instances of the C<Apache::Test> framework.
+if you happen to run many instances of the C<Apache-Test> framework.
 The I<-port=select> option helps such situations. This option will
 automatically select the next available port. For example if you
 run:
@@ -273,7 +273,7 @@
 use the same port, because when the server is configured it only tests
 whether the port is available but doesn't call bind() immediately. This
 race condition needs to be resolved. Currently the workaround is to
-start the instances of the C<Apache::Test> framework with a slight delay
+start the instances of the C<Apache-Test> framework with a slight delay
 between them. Depending on the speed of your machine, 4-5 seconds can be
 a good choice, as this is the approximate the time it takes to configure
 and start the server on a quite slow machine.
@@ -410,7 +410,7 @@
 still be seen in production, but this testing greatly minimizes such a
 possibility.
 
-The C<Apache::Test> framework provides a few options useful for stress
+The C<Apache-Test> framework provides a few options useful for stress
 testing.
 
 =over
@@ -1267,7 +1267,7 @@
 =head2 Special Configuration Files
 
 Some of the files in the F<t/conf> directory have a special meaning,
-since the C<Apache::Test> framework uses them for the minimal
+since the C<Apache-Test> framework uses them for the minimal
 configuration setup. But they can be overriden:
 
 =over
@@ -1432,7 +1432,7 @@
 use the C<Apache::Constants> module instead [/F].
 
 The configuration part for this test will be autogenerated by the
-C<Apache::Test> framework and added to the autogenerated file
+C<Apache-Test> framework and added to the autogenerated file
 F<t/conf/httpd.conf> when C<make test> or C<./Build test> or C<t/TEST
 -configure> is run. In our case the following configuration section will
 be added:
@@ -1683,7 +1683,7 @@
 If you have LWP (libwww-perl) installed its C<LWP::UserAgent> serves
 as an user agent in tests, otherwise C<Apache::TestClient> tries to
 emulate partial LWP functionality. So most of the LWP documentation
-applies here, but the C<Apache::Test> framework provides shortcuts
+applies here, but the C<Apache-Test> framework provides shortcuts
 that hide many details, making the test writing a simple and swift
 task. Before using these shortcuts C<Apache::TestRequest> should be
 loaded, and its import() method will fetch the shortcuts into the
@@ -1740,7 +1740,7 @@
 
 =back
 
-These are two special methods added by the C<Apache::Test> framework:
+These are two special methods added by the C<Apache-Test> framework:
 
 =over
 
@@ -1901,7 +1901,7 @@
 
 =head2 Starting Multiple Servers
 
-By default the C<Apache::Test> framework sets up only a single server
+By default the C<Apache-Test> framework sets up only a single server
 to test against.
 
 In some cases you need to have more than one server.  If this is the
@@ -1937,7 +1937,7 @@
 
 =head2 Multiple User Agents
 
-By default the C<Apache::Test> framework uses a single user agent
+By default the C<Apache-Test> framework uses a single user agent
 which talks to the server (this is the C<LWP> user agent, if you have
 C<LWP> installed). You almost never use this agent directly in the
 tests, but via various wrappers. However if you need a second user
@@ -1954,7 +1954,7 @@
 sub-tests may not hit the same server instance. In certain tests
 (e.g. testing the closure effect or the C<BEGIN> blocks) it's
 important to make sure that a sequence of sub-tests are run against
-the same server instance. The C<Apache::Test> framework supports this
+the same server instance. The C<Apache-Test> framework supports this
 internally.
 
 Here is an example from C<ModPerl::Registry> closure tests. Using the
@@ -3140,7 +3140,7 @@
 variables. The I<perldebug> and the I<perldebtut> manpages are
 covering the Perl debugger in fine details.
 
-The C<Apache::Test> framework extends the Perl debugger and plugs in
+The C<Apache-Test> framework extends the Perl debugger and plugs in
 C<LWP>'s debug features, so you can debug the requests. Let's take
 test F<apache/read> from mod_perl 2.0 and present the features as we
 go:



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org