Parsed XML test README

Using the test suite

 This directory holds our test suite.  Usually, it can be invoked with
 "python domtester.py".  Appending an -h argument will return a usage
 string. 

 To run the domtester, you need to be able to find Zope's unit testing
 framework and mount the ZODB, so you need to make sure Zope's lib/python
 can be found. Adding Zope's lib/python to your python path, either
 going through sys.path or adding it to the PYTHONPATH environment variable.
 For instance, if you're running bash, all you have to type is this::

   export PYTHONPATH=/path/to/Zope/lib/python

 The ZODB must also be mountable, so if you're not running ZEO, the
 server must be stopped while the tests run.

 Upon completion, the tester will report how many tests failed, and
 put more detailed output in out.txt.

Running tests individually

 You can also run each test individually, for instance::

   python test_dom.py

 Again you have to make sure Zope's lib/python can be found.

 There's also a very simple test_all.py that runs all the individual
 tests in a row; doing the same thing as domtester.py does but without
 some of the conveniences.

Debugging with the test suite

 If you want to contribute changes to ParsedXML, please run the test
 suite to make sure that your changes don't break anything.

 The tests themselves are in test_domapi.py.

 The test suite checks for compliance with the Python IDL mapping with
 the DOM specification.  As of this writing nearly all of DOM level 2
 is tested, along with a few level 3 interfaces.

 Some Parsed XML specific tests are run as well, if the implementation
 supports those features, such as persistence, parsing, and printing.

 The suite is very useful for testing extensions to Parsed XML that
 provide full DOM capabilities.  We run the tests on both our
 ManageableDOM and DOM layers - if it works for DOM, it should work
 for ManageableDOM, which proxies the entire DOM interface.
