"Theodore W. Leung" wrote: > in the spirit of 2, I've checked in a modification to build.xml that > allows a developer to fetch a copy of the xmlconf test suite from > sourceforge, and to then run both validating and non-validating reports > on Xerces. Curiously enough, when I did this, I found some failures.
Arnaud is right, the "standard" test suite contains errors. I know that I had to fix some bugs in the XML script used to drive the conformance test as well as repair the damage caused by CVS/tar to newlines, etc. on the expected output. Hopefully this situation will improve in the next version of the suite. So when I run tests, I use my augmented conformance suite of files. And even with that I get some spurious errors. So I run the tests twice: once before affecting a change and again afterwards. Then I compare the results of both to see if there are any regressions. -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
