W3C home > Mailing lists > Public > www-dom-ts@w3.org > August 2001

New EE variants of NoModificationAllowed.xml's, most tests now option safe

From: Curt Arnold <carnold@houston.rr.com>
Date: Thu, 23 Aug 2001 03:18:10 -0500
Message-ID: <000001c12be2$229f6800$a800a8c0@CurtMicron>
To: <www-dom-ts@w3.org>
Since expanding entities on load is an acceptible behavior, I've added siblings of all the *NoModificationAllowedErr tests with an EE suffix (for entity expansion) which tests the same behavior using created entity references instead of loaded entity references.

I've made most of the tests safe for different parser settings.  Tests are most commonly affected by expandEntityReferences and ignoringElementContentWhitespace.  Some DOM are hardwired to a particular setting (Xerces-C always expands entity references, Batik ignores element content whitespace).  The harness runs the test suite twice, once with the default settings and then once with complementary settings.

Tests that declare <implementationAttribute> immediately after the metadata element will modify the default DocumentBuilderFactory for the test pass to their needs.  So in the second pass when most tests are expanding entity references, ...NoModificationAllowedErr tests will not expand entity references but will keep all the other settings.
Received on Thursday, 23 August 2001 10:44:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:03 UTC