[STATUS] (perl-framework) Wed May 14 23:46:22 EDT 2003

[Rodent of Unusual Size]

httpd-test/perl-framework STATUS:   -*-text-*-
Last modified at [$Date: 2002/03/09 05:22:48 $]

Stuff to do:
* finish the t/TEST exit code issue (ORed with 0x2C if
  framework failed)

* change existing tests that frob the DocumentRoot (e.g.,
  t/modules/access.t) to *not* do that; instead, have
  Makefile.PL prepare appropriate subdirectory configs
  for them.  Why?  So t/TEST can be used to test a
  remote server.

* problems with -d perl mode, doesn't work as documented
  Message-ID: [EMAIL PROTECTED]
  Date: Sat, 20 Oct 2001 12:58:33 +0800
  Subject: Re: perldb

Tests to be written:

* t/apache
  - simulations of network failures (incomplete POST bodies,
chunked and unchunked; missing POST bodies; slooow
client connexions, such as taking 1 minute to send
1KiB; ...)

* t/modules/autoindex
  - something seems possibly broken with inheritance on 2.0

* t/ssl
  - SSLPassPhraseDialog exec:
  - SSLRandomSeed exec:

running tests as root

[Geoffrey Young]

hi all...
  I'm actually in the situation where I need to run Apache with 'User root' 
(yes, I know, I know...)

  anyway, I'd like to write tests for that situation, but 
TestConfig::default_user() won't let me run tests as root and setting User 
in extra.conf.in (so that there are two User settings) doesn't seem to 
effect Apache in 1.3.

  is there a particular reason this restriction is coded in such a way that 
I can't get around it, no matter what, if I _want_ to run Apache as root?

--Geoff