Product Tests

Richard Brooksby, Ravenbrook Limited, 2000-12-13

1. Introduction

This document lists the tests which have been written to measure the quality of the Perforce Defect Tracking Integration product.

This document will be updated as new tests are created.

The readership of this document is anyone developing or extending the product sources.

This document is not confidential.

These tests use the Python unit test framework [PyUnit]. To use the framework with these tests, put the module unittest.py from the PyUnit distribution on Python's library path. New unit test scripts should be called test_module.py, where module.py is the module being tested. Each test script should define a function called tests, which returns an object belonging to the unittest.TestSuite class. The run_tests.py script finds all tests in the current directory and runs them.

To run the unit test for the message module, run the command python test_message.py.

To run the "wrapping" test case (only) from the unit test for the message module, run the command python test_message.py wrapping.

To run all the tests in this directory, run the command python run_tests.py.

run_tests.py Run all tests.

3. Unit and integration tests

`test_catalog.py`	Unit test for the `catalog` module.
`test_check_config.py`	Unit test for the `check_config` module.
`test_message.py`	Unit test for the `message` module.
`test_p4dti.py`	Tests of the P4DTI (starting, configuration, operation, errors, ...).
`test_translator.py`	Unit test for the `translator` module.

4. System tests

`config_sandpiper.py`	Test configuration for running the P4DTI with TeamTrack on sandpiper.ravenbrook.com.
`perforce_sample_data.py`	Script that generates a sample Perforce repository and which generates bug-fixing activity in that repository.
`teamtrack.txt`	Test procedure for TeamTrack integration.
`teamtrack-test.mdb`	Sample TeamTrack database, for use with the TeamTrack test procedure.
`teamtrack_sample_data.py`	Script that adds sample P4DTI data to a TeamTrack database (it was used before the P4DTI had all its features). Now obsolete and incorrect.

A. References

[PyUnit]

"PyUnit - a unit testing framework for Python"; Steve Purcell.

B. Document History

2000-12-13	RB	Created as placeholder.
2001-02-27	GDR	Added TeamTrack test procedure, sample TeamTrack database, and two test scripts.
2001-03-02	RB	Transferred copyright to Perforce under their license.
2001-03-13	GDR	Added test framework (section 2) and unit tests (section 3); old test material is now under the heading "system tests" (section 4).
2001-03-14	GDR	Added `test_catalog.py` and `test_check_config.py`.

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: //info.ravenbrook.com/project/p4dti/branch/2001-03-12/integration-kit/test/index.html#7 $