We faced a similar challenge in our port of subversion to the IBM iSeries,
namely that we run the test scripts from a Windows client (XP pro SP2 in
our case) against our iSeries server. Unfortunately I haven't gotten
around to making any generic scripts to do this, but what follows is how
I've made this work and if you change the path names to protect the
innocent perhaps it will be useful to you.
1) Map a drive 'Z:' on your Win box to the root of your remote NetWare
server (I know nothing about NetWare and am assuming you can do this...if
not this probably won't help you).
2) Create two identical test paths on your Win box and the NetWare server:
3) Place the appropriate location directives in your httpd.conf file:
4) Apply the attached patch to
5) Start your Apache server
6) Run the tests from your client:
C:\SVN\src-trunk>win-tests.py -r -f fsfs -u http://Zeus:8099
7) Bathe in the glory of all those "*.py...success" messages :-)
Hope that helps.
SoftLanding Systems, Inc.
NormW <email@example.com> wrote on 05/14/2005 04:33:01 AM:
> What I haven't done up to this point is actually get time to test the
> resulting nlm's. I suspect svnserve will be a major headache (on the
> NetWare platform), so would like to try some testing from a remote
> client through the apache/webDAV interface. Are there any 'generic'
> scripts that I can run on a Win2K box that will exercise the NetWare
> modules running on another machine?
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Mon May 16 17:39:35 2005
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com