P4DTI issue job000075

TitleNo automatic check of configuration
Statusclosed
Priorityessential
Assigned userGareth Rees
OrganizationRavenbrook
DescriptionHow do you tell if the configuration is correct? There should be automatic checking of the configuration.
See e-mail "Checking the configuration automatically" for some ideas.
AnalysisThe replicator shouldn't assume that the configuration is correct, but should check it.
We could have an external checking script that does a really thorough job.
See also GDR's list of things to check at <http://info.ravenbrook.com/mail/2000/10/24/23-13-26/0.txt>.
The replicator should check aspects of the TeamTrack workflow, as described in section 3.2 of the AG; when problems are discovered it should give a warning, and the warning should appear in section 13.2 of the AG. GDR 2001-01-02.
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dti/doc/2000-10-23/teamshare-psg-alpha-test/> item 19
Observed in0.3.2
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 6
Created byRichard Brooksby
Created on2000-11-23 14:12:32
Last modified byGareth Rees
Last modified on2001-12-10 19:03:34
History2000-11-23 RB Created from sources (see evidence).
2001-01-02 GDR Added note about workflow checks.

Fixes

Change Effect Date User Description
7565 closed 2001-01-23 18:16:58 Gareth Rees Adding unmatched_users method to TeamTrack user translator.
7554 open 2001-01-23 16:28:30 Gareth Rees The function check_email() now checks that the address is an RFC822 address spec.
7552 open 2001-01-23 16:01:40 Gareth Rees The p4 module now checks that Perforce client version is supported.
5348 open 2000-12-04 10:07:54 Gareth Rees Check that replicator's RID and defect tracker's RID match.
5127 open 2000-11-29 18:51:18 Gareth Rees Fixed bug: error changed to self.error.