Mime-Version: 1.0
Message-Id: <p05001939b6a717de51ed@[172.16.1.164]>
Date: Sun, 11 Feb 2001 11:01:58 +0000
To: p4dti-staff@ravenbrook.com
From: Gareth Rees <gdr@ravenbrook.com>
Subject: Test report for release 0.4.2, 2001-02-07
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

We installed P4DTI 0.4.2 on a Windows 2000 machine at Lycos.  We were 
installing it in a configuration where the SQL Server database was on 
a different machine from the TeamTrack server, but the latter was on 
the same machine as P4DTI.  Lycos' internal network is very slow.  My 
connection to perforce.ravenbrook.com over a modem was about as fast 
as the connection to Lycos' Perforce server on the local network.

1. David Markley points out that we shouldn't have to ask people to 
run regedit.  Instead we can ship a ".reg" file; when this is 
double-clicked, registry entries get added.  You can see the format 
of a ".reg" file by exporting settings from regedit.

2. We got a "Perforce error: You don't have permission for this 
operation"; the cause of this was that the p4_user had different case 
in the config and in Perforce.

3. The documentation is generally inadequate.  There's too much 
information.  People just don't want to read it.

4. The integration reads the whole CASES table when it starts up. 
This is a big problem when there are thousands of cases and the 
network is slow.

5. The integration reads the USERS table every time it misses a user. 
This is a big problem when there are hundreds of users and the 
network is slow.

6. When using the integration from the command line, I set up a 
jobview in my user settings and ran "p4 submit".  I was expecting to 
see something like the following:

Jobs:
	BUG000123 ignore # A bug

but instead I saw:

Jobs:
	BUG000123 # A bug

and Perforce refused to let me type the status after the bug name. 
Both server and client were 2000.2, downloaded that day from Perforce.