On Thu, 2002-05-16 at 08:40, Andy Clark wrote: > > * Whenever making changes that affect multiple components, > the changes need to be tested *thouroughly*. This > generally means: > > 1) performing a "build clean all" > 2) running conformance tests > 3) running any other applicable tests > > And this needs to be done BEFORE committing the change. >
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. Also at the moment, the report files begin with garbage because ant captures both stderr and stdout to the same file, and the conformance test suite driver doesn't have a way to specify an output file for the test. Ted --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
