perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject cvs commit: modperl-docs/src/devel/writing_tests writing_tests.pod
Date Sat, 22 Sep 2001 09:51:04 GMT
stas        01/09/22 02:51:03

  Modified:    src/devel/writing_tests writing_tests.pod
  Log:
  document the recently added <Base>...</Base> block functionality
  
  Revision  Changes    Path
  1.8       +34 -4     modperl-docs/src/devel/writing_tests/writing_tests.pod
  
  Index: writing_tests.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/devel/writing_tests/writing_tests.pod,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- writing_tests.pod	2001/09/19 09:02:36	1.7
  +++ writing_tests.pod	2001/09/22 09:51:03	1.8
  @@ -147,7 +147,7 @@
   For more details about the C<Test::Harness> module please refer to its
   manpage.
   
  -=head2 One Part Perl tests: Response only
  +=head2 One Part Perl Tests: Response only
   
   If you write only a response part of the test, C<Apache::Test> will
   automatically generate the corresponding test part that will generated
  @@ -219,7 +219,7 @@
   
   so when you run your new tests the new configuration will be added.
   
  -=head2 Two parts Perl tests: Request and Response
  +=head2 Two Parts Perl Tests: Request and Response
   
   But in most cases you want to write a two parts test where the client
   (request) parts generates various requests and tests the responses.
  @@ -739,8 +739,8 @@
     __DATA__
     PerlRequire "Foo.pm"
   
  -these will be wrapped into the E<lt>LocationE<gt> section and placed
  -into configuration file for you:
  +these will be wrapped into the C<E<lt>LocationE<gt>> section and
  +placed into configuration file for you:
   
     <Location /TestResponse::nice>
        SetHandler modperl
  @@ -748,6 +748,33 @@
        PerlRequire "Foo.pm"
     </Location>
   
  +If some directives are supposed to go to the base configuration,
  +i.e. not to automatically wrapped into C<E<lt>LocationE<gt>> block,
  +you should use a special C<E<lt>BaseE<gt>>..C<E<lt>/BaseE<gt>>
block:
  +
  +  __DATA__
  +  <Base>
  +      PerlSetVar Config ServerConfig
  +  <Base>
  +  PerlSetVar Config LocalConfig
  +
  +Now the autogenerated section will look like this:
  +
  +  PerlSetVar Config ServerConfig
  +  <Location /TestResponse::nice>
  +     SetHandler modperl
  +     PerlResponseHandler TestResponse::nice
  +     PerlSetVar Config LocalConfig
  +  </Location>
  +
  +As you can see the C<E<lt>BaseE<gt>>..C<E<lt>/BaseE<gt>>
block has
  +gone. As you can imagine this block was added to support our virtue of
  +lazyness, since in most tests don't need to add directives to the base
  +configuration and we want to keep the configuration size in test
  +minimal and let Perl do the rest of the job for us.
  +
  +META: Virtual host?
  +
   META: to be completed
   
   =head2 Tests with Non-threads perl versus threaded Perl
  @@ -759,6 +786,9 @@
     <IfDefine PERL_USEITHREADS>
         ... configuration bits
     </IfDefine>
  +
  +C<Apache::Test> will start the server with -DPERL_USEITHREADS if the
  +Perl is ithreaded.
   
   For example C<PerlOptions +Parent> is valid only for the threaded
   perl, therefore you have to write:
  
  
  

Mime
View raw message