Re: Testing remote server

[john sachs <js...@covalent.net>]

as was mentioned earlier, some test write to the server root, perhaps we could add a special directive so you could do something like this in your plan line:

plan tests => 5, have_module 'foo' && have_local_server_root

where 'have_local_server_root' could be named whatever we think appropriate and is set to 1 unless -servername is specified on the command line.

then tests that require access to server root could be skipped when you are testing on a remote host.

whatchooguysthink?
-j

On Tue, Dec 04, 2001 at 02:50:07PM -0500, Rodent of Unusual Size wrote:
+ Doug MacEachern wrote:
+ > 
+ > > Not without some trickery: loads of the scripts rely on being able to
+ > > write directly to the server root.
+ > 
+ > we should fix that.  the original plan was for this to work:
+ > % t/TEST -run -port 8080 -servername foo
+ > 
+ > and have the .t's hit http://foo:8080
+ 
+ Was 'foo' supposed to be a vhost on the current system, or
+ was it supposed to be able to be a remote system?  The
+ latter is my goal (testing things like DAV on Win32 bites
+ the Harry Houdini..).
+ -- 
+ #ken	P-)}
+ 
+ Ken Coar, Sanagendamgagwedweinini  http://Golux.Com/coar/
+ Author, developer, opinionist      http://Apache-Server.Com/
+ 
+ "All right everyone!  Step away from the glowing hamburger!"