Message-Id: <5.0.2.1.0.20010305141728.00a57d90@pop3.ravenbrook.com>
Date: Mon, 05 Mar 2001 16:16:40 +0000
To: p4dti-staff@ravenbrook.com
From: Gareth Rees <gdr@ravenbrook.com>
Subject: Test report for TeamTrack release 1.0.2, 2001-03-05
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

1. TeamTrack names the wrong user in an error message: I was logged into 
Perforce as user "lmb" and set the state of a job to "assigned"; the 
corresponding user in TeamTrack didn't have the privilege to make this 
transition.  I was expecting to get the error message "User lmb does not 
have privilege for transition Assign." but instead I got "User 
P4DTI-replicator0 does not have privilege for transition Assign."

2. TeamTrack fails to name the Update transition in an error message: If 
you edit an issue without permission, you get an error from TeamTrack like 
this: "User P4DTI-replicator0 does not have privilege for transition 
."  This isn't very helpful.

3. TeamTrack silently resets incorrect values: If a value in a 
single-select field is disabled for a project, and I use Perforce to set 
that field to the disabled value in a job belonging to that project, then 
TeamTrack silently resets the value for that field to (None).

4. There's a poor error message when you edit an issue as a Perforce user 
with no corresponding user in TeamTrack: If I'm logged into Perforce as a 
user with no corresponding user in TeamTrack and I edit a job, then I get 
an e-mail with the unhelpful error message "(no message from the TeamShare 
API)".

5. Changelist links go to the frame, not the whole page: If the 
changelist_url is set up and working, then if you click on one of the 
changelist links in the "Perforce fixes" table in TeamTrack, the changelist 
information shows up in the frame, not filling the whole page.  This looks 
poor, because the TeamTrack look-and-feel is very different from the 
Perforce look and feel.

6. Suppose you start out with closed_state=None and people make fixes in 
Perforce to the state "resolved".  Then you set closed_state="resolved" and 
run the refresh script.  This fails because it tries to make fixes to the 
state "resolved", which Perforce refuses because there is no Perforce state 
"resolved" (Perforce now uses "closed" instead).

7. If you run the refresh.py script as your first step (before ever running 
the run.py script) then when you come to run the run.py script all the jobs 
get overwritten.

8. There are mysterious TeamTrack errors in the Windows Application Log 
looking like this:

'D:\Reflex\Db\AppRecordList.cpp', line 84.

     The record list with the 'select * from TS_VCACTIONS where TS_TYPE=3 
and TS_INFO1 in (  )' select statement could not be read from the 
'VCActions' table.

     Syntax error (missing operator) in query expression 'TS_TYPE=3 and 
TS_INFO1 in (  )'.

This is not a replicator error, because no such query can be generated by 
dt_teamtrack.py.