Received: from [193.112.141.254] (grouse.ravenbrook.com [193.112.141.254]) by raven.ravenbrook.com (8.9.3/8.9.3) with ESMTP id NAA00576 for ; Fri, 27 Apr 2001 13:54:09 +0100 (BST) Mime-Version: 1.0 X-Sender: gdr@pop3 Message-Id: Date: Fri, 27 Apr 2001 13:25:45 +0100 To: p4dti-staff@ravenbrook.com From: Gareth Rees Subject: Test report for release 1.0.5, 2001-04-26 Content-Type: text/plain; charset="us-ascii" ; format="flowed" This is a report based on observing use of P4DTI 1.0.5 at Reef. 1. The P4DTI administrator had set up test TeamTrack and Perforce servers, with many example users. So that the many e-mail messages sent by the replicator would go to him, he set the e-mail addresses of all the sample users to his e-mail address. As a consequence of this, all the TeamTrack users got mapped to the same Perforce user (the P4DTI replicator). So when an issue was replicated to Perforce, it because owned by the P4DTI replicator user, and changes couldn't be replicated back because that user had no permission to update issues in TeamTrack. I made job000308 for this . 2. The TeamTrack workflow had a number of deleted states. These all showed up in the states menu in Perforce. This was very annoying. It seems to me that this is a real problem that we should think about seriously. So I re-opened job000145 . 3. There's a Perforce bug whereby underscores don't work in jobviews. Since the replicator translates spaces to underscores in keyword fields like the job status, many people will want to have a jobview like "owner=me state=ready_for_test". But this won't work. We saw this during alpha testing and reported the bug to Perforce support some time ago, but we didn't note that it was P4DTI dependent. So I've created job000309 for this . 4. We saw the mysterious error message "User p4dti-replicator0 does not have privilege for transition ." (see job000305) when the replicator tried to replicate a job that was owned by a user in Perforce who had no corresponding user in TeamTrack. I added this observation to job000305 .