Mime-Version: 1.0
Message-Id: <p05001906b693667d13f1@[193.112.141.254]>
Date: Tue, 23 Jan 2001 17:00:54 +0000
To: p4dti-staff@ravenbrook.com
From: Gareth Rees <gdr@ravenbrook.com>
Subject: Test report for 0.4.2, 2001-01-22
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

These issues came up while installing and testing P4DTI release 0.4.2 
with Robert Cowham on 2001-01-22.

1. Robert thought that there should be a readme file with the 
distribution, since many sysadmins are used to the download - unpack 
- read the readme sequence of operations.  This could just be a file 
saying "Now read the AG".

2. config_teamtrack.py is delivered read-only, but the AG tells you 
to edit it.  This is more awkward than it need be.  I was surprised 
not to have seen this before, but I note that Robert had downloaded 
the .zip rather than the .exe from our website.  Perhaps WinZip 
preserves permissions but self-extracting archives don't?

3. Robert's machine hung when he started the integration.  It turned 
out that this was because he was running the ZoneAlarm application, 
which snoops on all network traffic and asks for confirmation before 
it will let a new application make a network connection.  It needed 
to be told before it would let the P4DTI make connections to 
TeamTrack and Perforce, even on the same machine.

4. We had set smtp_server to 'smtp.ravenbrook.com' but this was 
refusing connections.  The effect of this in the replicator was to 
get an error in the log "socket.error: (10222, 'invalid argument')".

5. Robert set teamtrack_host to 'localhost'.  But this didn't work in 
Windows 2000.  We got a SOCKET_CONNECT error.

Otherwise, it all seemed to work in Windows 2000.