RELEASE TEST PROCEDURE

             Richard Brooksby, Ravenbrook Limited, 2001-03-21


1. INTRODUCTION

This is the basic minimum test procedure to be applied to all releases
of the P4DTI software.

The readership of this document is project engineers.

This document is not confidential.


2. PROCEDURE

1. Clean your machine.  Remove previous installations of P4DTI,
Bugzilla, TeamTrack, and other software.

For a really thorough test, remove all prerequisite software, or
start with a completely virgin machine with a freshly installed
operating system.

2. Obtain the release.

   - Check that links to the release are correct.

   - Check that the release is correctly described.

   - Read and follow the instructions that accompany the release (the
readme.txt) file.

3. Verify that all the prerequisites are met.

   - Ask Perforce for its version and check it against the manual.

   - Ask Python what version it is and check it against the manual.

   - Inspect the TeamTrack build number.

   - Make sure you're running an _unpatched_ Bugzilla.

4. Install test repository, databases, etc. from the test materials
for the relevant version (e.g. teamtrack-test.mdb).  These should be
constructed to meet the various "procedural prerequisites".

5. Copy the configuration for the test machine from the test
materials for the relevant version.  Check it over by eye.

6. Follow the AG instructions for patching Bugzilla, updating the
registry, etc.

7. Start the replicator as described in the manual and compare the
output to that in the manual.  Stop it as described.  Start it again.
On Linux, test the startup script for starting and stopping the
replicator.  Reboot the machine to make sure it starts automatically
as described.

8. Follow the instructions in the manual for testing the
configuration.  (i.e. take an issue through a complete life cycle as
described in the UG, from various Perforce interfaces, and run
"check.py").  Deliberately simulate various user errors and
violations of permissions to check e-mail delivery and accuracy.
Look up error messages in the AG.

9. Run any automatic tests to stress the system.

10. Change the set of users and a user's e-mail address and re-start
the replicator to make sure it picks up the new configuration, as
described in "Maintaining the P4DTI".

11. Change the set of replicated fields and refresh the Perforce jobs
as described in "Maintaining the P4DTI".

12. Leave it running for as long as possible.

13. Uninstall the integration, following the instructions in the AG.
Make sure that Perforce and the DT are still functioning.

14. Test the TeamTrack integration in the three configurations we
support: TeamTrack 4.5, TeamTrack 5.0, and TeamTrack 5.0 with a database
upgraded from TeamTrack 4.5.


A. REFERENCES


B. DOCUMENT HISTORY

2001-03-21 RB Drafted in e-mail.

2001-03-26 RB Edited into shape as text document in master sources.

2001-07-05 GDR Test TeamTrack in all three configurations.

---

This document is copyright (C) 2001 Perforce Software, Inc.  All rights
reserved.

Redistribution and use of this document in any form, with or without
modification, is permitted provided that redistributions of this
document retain the above copyright notice, this condition and the
following disclaimer.

THIS DOCUMENT IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDERS AND CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

$Id$