About DOM . DOM Activity statement
Technical Reports . Technical Materials
Test Suites . Test Suites FAQ . Mailing Lists
Members only resource: DOM Working Group

DOM Conformance Test Suite, Level 3 Validation

This document describes how to run the DOM Level 3 Validation Test Suite. It also includes pointers to relevant software as well as relevant resources.

The DOM TS has been developed in accordance with the DOM Conformance Test Suites Process Document. For additional information and to download other DOM Test Suites, visit the DOM Conformance Test Suites page.

The DOM Conformance Test Suite consist of a series of tests that have been generated from XML test descriptions, then transformed into the two official DOM bindings, Java and ECMA. In order to run the test suite, we have provided the possibility to run the tests using the JUnit and JsUnit testing frameworks, both included in this distribution.

The DOM Level 3 Validation test suite was released TBD.

Download the latest version of the DOM Level 3 Validation Test Suite.

This distribution is organized as follows:

The DOM TS currently tests XML, XHTML and SVG implementations of DOM Level 3 Validation.

To run the ECMAScript tests, open ecmascript/level3/validation/alltests.html in the browser you want to test. Configure the implementation, test document loading parameters and content type and press run.

Running the Java tests will require placing a JAXP 1.1 compatible parser on the classpath or placing a common JAXP 1.1 parser (Apache Xerces or Oracle XML Developer Kit) in the java/ directory.

Running "java -jar dom3-validation.jar" from the java/ directory will write to the console a summary of the parser under test and the results of the tests run in two distinct configurations. The parser under test can be selected by any mechanism supported by JAXP 1.1.

The Java tests may also be run using from JUnit TestRunner's. To run all tests against the default JAXP parser in a default configuration from the JUnit text user interface, run " java -classpath dom3-validation.jar junit.textui.TestRunner org.w3c.domts.level3.validation.TestDefaultParser". The run the Swing or AWT user interfaces, replace "textui" with "swingui" or "awtui" and add "-noloading" before the test case to not use JUnit's custom ClassLoader, for example, "java -classpath dom1-validation.jar junit.swingui.TestRunner -noloading org.w3c.domts.level3.validation.TestDefaultLS"

Running "java -jar junit-run.jar" will launch the JUnit SwingUI without the custom ClassLoader.

The following TestSuite's are provided for use within JUnit TestRunner's. These provide the only mechanism for testing implementations that do not support JAXP 1.1 such as Batik or DOM4J.

We look forward to your comments. The DOM TS Group communicates primarily through the DOM TS mailing list (archive).

Tests in this table are released under the W3C Software Copyright Notice and license:
Copyright © 2001-2004 World Wide Web Consortium, (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University). All Rights Reserved. This work is distributed under the W3C® Software License in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

The DOM TS was jointly launched by the W3C and NIST. It is, however, a publically developed and open framework. Reaching the point of being able to finalize and release the DOM TS would not have been possible were it not for the contribution from several people in the developer community, especially Curt Arnold and Fred Drake.