Received: from [10.1.2.31] (root@raven.ravenbrook.com [193.82.131.18]) by raven.ravenbrook.com (8.9.3/8.9.3) with ESMTP id VAA25160 for ; Tue, 24 Jul 2001 21:58:59 +0100 (BST) Mime-Version: 1.0 X-Sender: gdr@pop3 Message-Id: Date: Tue, 24 Jul 2001 14:58:52 -0600 To: p4dti-staff@ravenbrook.com From: Gareth Rees Subject: Release 1.1.3 test report Content-Type: text/plain; charset="us-ascii" ; format="flowed" 1. The test scripts in the integration kit don't work if socket.gethostname() returns an upper-case hostname, as it does under Windows 2000. 2. We encountered the "can't update issue in TeamTrack" bug . We couldn't reproduce this in the latest API (build 50101). So we tried rebuilding the P4DTI interface using build 50101. This time it worked. That suggests that there's a bug in the version of the API that I've been building with and I need the 50101 API. 3. In the integration kit, the Python interface to TeamTrack's shell.py doesn't work properly in the release configuration (because it adds ..\build\debug to sys.path but not ..\build\release). We probably need two shells, say shell_debug.py and shell_release.py. 4. The integration kit doesn't explain how to get the automated test cases running. You need to download the Python extensions for Win32 from , download unittest.py and put it in the test directory.