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 OAA23664 for ; Tue, 24 Jul 2001 14:44:14 +0100 (BST) Mime-Version: 1.0 X-Sender: gdr@pop3 Message-Id: Date: Tue, 24 Jul 2001 07:08:54 -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" This is a report describing the testing of release 1.1.3 at TeamShare. 1. The P4DTI couldn't connect to a TeamTrack web server running on the address https://raidpc/. The P4DTI hung for a minute or so, and then stopped with the error TeamShare API error: SERVER_ERROR: Server error: -1. We couldn't connect to that server using a TeamShare API sample application either. We verified that the TeamTrack server was up and running and that the user existed (by connecting using Internet Explorer to the TeamTrack web page). This suggests that the TeamShare API doesn't support secure HTTP and hence the P4DTI doesn't support TeamTrack running on a secure web server. It turns out that this is because the socket library we have been linking with (ws2_32.dll) doesn't support SSL. You have to use wininet and MFC. Could we rebuild the Python interface to TeamTrack to link with wininet and make it work that way? The AG and the release notes need to explain that we don't support TeamTrack on a secure web server. The AG needs to say something about the error message in section 11.2. 2. Building the Python/TeamTrack interface from the Integration Kit is not straightforward. You have to make sure that paths for Python 2.0 are correct before you can compile, link and run from Visual Studio. The design document needs to explain this. 3. The AG mentions P4DTI_ACTION in Figure 4, but this field is no longer used. 4. You can get this error if you haven't given the replicator user "Connect using API" privilege: TeamShare API error: SOCKET_READ_ERROR: Socket error. However, the AG omits to say so. 5. The AG has a wrong download URL for TeamTrack. TeamShare say that they cannot guarantee any URL on their web site will stay valid, so the AG should say "Start at http://www.teamshare.com/ and look about for the download." 6. The AG ought to specify configuration parameters in a sensible order for filling them in. The order in config.py is probably a good one. 7. The AG says "C:\Program Files\P4DTI" in at least one place. This needs correcting. (It's "C:\Program Files\P4DTI-RELEASE" now.) 8. If you specify a non-existent host for the smtp_server configuration parameter, then you get this error: socket.error: host not found This means that smtp_server is not correct. The AG should document this error in section 11.3. 9. TeamTrack 5.0 adds an option for text fields: they can be "Journal" fields like the longdesc field in Bugzilla. These fields are not properly supported by the P4DTI. 10. Journal fields aren't recognized as being multi-line text fields (because they have field type 101 and attribute 3, which isn't recognized in configure_teamtrack.py). When you try to replicate such a field, the replicator refuses because Perforce won't update the job: it complains of a syntax error in the job form. This turns out to be because the journal field wasn't going through the text_translator and so doesn't have a newline at the end. We worked around this during the test by recognizing journal fields as multi-line text fields: if tt_field_type == 101 and f['ATTRIBUTES'] in [0,3]: But what does attribute = 2 mean? Is that another kind of multi-line text field? The TeamTrack database schema doesn't mention journal fields and doesn't explain any attributes other than 0 and 1. I think it's also a bug in Perforce not to be able to parse a text field without a newline at the end. 11. job000362. We were able to reproduce this using Derek George's database: when connected to the server as P4DTI then a call to transition('dgeorge',0) failed as described in the job. We gave dgeorge and P4DTI a bunch of extra privileges (namely, Submit, Update and Transition for all issues in the projects to be replicated) and the call succeeded. So the AG needs to change the privileges it recommends you give to the replicator, the readme.txt should perhaps mention this in the upgrade instructions, and the AG needs to document the error message in 11.3. 12. This error: General error: unable to write to file buffer means that the TeamTrack server is out of disk space. 13. The Integration kit is generally inadequate in telling you how to get going with the test suite. For example, what preconditions do you need (in addition to the P4DTI preconditions, you need the Python Win32 extensions, and the Perforce server). Also, test configurations are very picky. You need to specify some extra config items (p4_server_executable, p4_license_file) and you need to have settings for start_date, closed_state, p4_port, replicated_fields that work with the config. This indicates poor test suite design. 14. In replicator.check_consistency, the variable 'issues' that should be 'issue_id_to_job'. (I thought we had fixed this?)