135N/A

548N/ACopyright 2008 Sun Microsystems, Inc. All rights reserved.

135N/AUse is subject to license terms.

135N/A

135N/A

135N/A 1. Summary

135N/A

135N/A The global test target, i.e. "make test", should be executed prior to

135N/A requesting code review and prior to integration. That target invokes

548N/A run.py in this directory.

548N/A

548N/A run.py drives the execution of our api and cli test suites, and

548N/A compares the results to a baseline file stored in baseline.txt.

548N/A

548N/A run.py can also be run standalone with a variety of options:

135N/A

548N/A Usage: run.py [-ghpv] [-b filename] [-o regexp]

548N/A -g Generate result baseline

548N/A -h This help message

548N/A -p Parseable output format

548N/A -v Verbose output

548N/A -b <filename> Baseline filename

548N/A -o <regexp> Run only tests that match regexp

548N/A

548N/A When adding, removing, or changing the results of test cases, make

548N/A sure to update baseline.txt and check it in. This can be done with the

548N/A -g option to run.py.

135N/A

135N/A 2. Pending work.

135N/A

548N/A The special dependency scenarios in "old" should be recoded as part of

548N/A the cli test suite.

135N/A

135N/A Targets to evaluate code coverage [1,2] should be added, possibly with

135N/A supporting global options added to each utility.

135N/A

135N/A 3. References

135N/A

135N/A [1] N. Batchelder, coverage module, 2007.

135N/A http://nedbatchelder.com/code/modules/coverage.html

135N/A

135N/A [2] C. T. Brown, figleaf module, 2006.

135N/A http://darcs.idyll.org/~t/projects/figleaf/README.html

135N/A

135N/A