Menu
▾
▴
[mvp-xml-cvs] XInclude/v2/test/XInclude-Test-Suite README.cvs,NONE,1.1 report.html,NONE,1.1 testcases.dtd,NONE,1.1 testdescr.xml,NONE,1.1 xinclude.xsl,NONE,1.1
|
From: Oleg T. <he...@us...> - 2005-10-28 22:29:42
|
Update of /cvsroot/mvp-xml/XInclude/v2/test/XInclude-Test-Suite In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv20225/v2/test/XInclude-Test-Suite Added Files: README.cvs report.html testcases.dtd testdescr.xml xinclude.xsl Log Message: --- NEW FILE: report.html --- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <META http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>XInclude Conformance Tests</title> <meta content="text/html;charset=utf-8" http-equiv="Content-Type"> <style type="text/css"> BODY { font-family: Lucida, Helvetica, Univers, sans-serif; } H2, H3, H4 { text-align: left; color: #0066CC; } </style> <style type="text/css"> a:hover { color: white; background-color: blue; [...3526 lines suppressed...] </table> </td><td bgcolor="#ccffff"> <p>Since the xpointer attribute is not a URI reference, %-escaping must not appear in the XPointer, nor is there any need for a processor to apply or reverse such escaping.</p> </td> </tr> </table> <a name="contrib"></a> <h3>4. Contributors (Non-normative)</h3> <p> A team of volunteer members have participated in the development of this work. Contributions have come from: </p> <ul> <li>Sandra I. Martinez, NIST</li> <li>Daniel Veillard, Red Hat Network</li> <li>John Evdemon, FourThought</li> <li>Richard Tobin, University of Edinburgh</li> <li>Elliotte Rusty Harold</li> </ul> </body> </html> --- NEW FILE: README.cvs --- <h1 align="center"><a href="http://www.w3.org/TR/xinclude">XInclude</a> Test Suite</h1> <p> This is the CVS base used to maintain the <a href="http://www.w3.org/XML/Test/XInclude/Overview.html">test suite</a> for the <a href="http://www.w3.org/TR/xinclude">XInclude</a> specification. <p> The file <em>testdescr.xml</em> describes the set of primary resources used by the test suite, the sections of the specification that are being checked, the author and date of each test. It also provide whether the test should fail with a fatal error or points to a result file if this is not the case. Please note that while we expect the testsuite to accurately reflect the XInclude specification it is not normative and may change if errors are found. <p> For more informations on the test suite or to download a packaged version of the tests, please visit the <a href="http://www.w3.org/XML/Test/XInclude/Overview.html">XInclude test suite page</a>. <p> This document has been produced by the <a href="http://www.w3.org/XML/Core/">W3C XML Core Working Group</a> as part of the <a href="http://www.w3.org/XML/">XML Activity</a>. <p> Feedback on the content of this test suite should be sent to the public mailing list <a href="mailto:www...@w3..." >www...@w3... </a> <a href="http://lists.w3.org/Archives/Public/www-xml-xinclude-comments/">(archive)</a>. --- NEW FILE: xinclude.xsl --- <?xml version='1.0'?> <!-- <<<<<<< xinclude.xsl Original version copyright 2002 by W3C. All Rights Reserved. ======= XSL Stylesheet for documenting XML Inclusions(XInclude) conformance tests. Tested against Xalan processor. >>>>>>> 1.0 XSL 2002-03-07 Stylesheet for documenting XInclude conformance tests. This expects to be run on a document matching the DTD that was defined for merging collections of self-descriptive XInclude tests. Since all those collections will have (by design) the same test architecture, this includes boilerplate describing that design, to be used by all test documentation. --> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output method="html" indent="yes"/> <!-- ROOT: write an HTML wrapper --> <xsl:variable name="root-path">http://xw2k.sdct.itl.nist.gov/carmelo/XInclude/</xsl:variable> <xsl:template match="/testsuite"> <!-- XHTML namespace --> <html><head> <title>XInclude Conformance Tests</title> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <style> <xsl:comment> BODY { font-family: Lucida, Helvetica, Univers, sans-serif; } H2, H3, H4 { text-align: left; color: #0066CC; } </xsl:comment> </style> <style> <xsl:comment> a:hover { color: white; background-color: blue; } </xsl:comment> </style> </head><body bgcolor='#ffffff'> <center><h1><font color="#0066cc">XInclude Test Suite</font></h1></center> <p/> <center> <table border="4" width="90%"> <tr > <td> <table> <tr > <td width="35%"><img src="http://www.w3.org/Icons/w3c_home" width="200" height="100"/></td> <td width="30%"/> <td width="35%" align="right"><img src="http://www.nist.gov/itl/div897/images/nist_home.gif" width="350" height="125"/></td> </tr> </table> <center> <table> <tr> <td ><b><font size="+2">A Joint Development Effort</font></b></td> </tr> </table> </center> </td> </tr> </table> </center> <p/> <h4>W3C XML Core Working Group<br/>XInclude 1.0 Test Suite<br/>13 February 2003</h4> <dl> <dt><b>This version:</b></dt> <dd><ul> <li><a href="http://xw2k.sdct.itl.nist.gov/carmelo/xinclude/xinclude.html"> http://xw2k.sdct.itl.nist.gov/carmelo/xinclude/xinclude.html</a> </li> </ul> </dd> <p/> <dt><b>Current version:</b></dt> <dd><ul> <li><a href="http://xw2k.sdct.itl.nist.gov/carmelo/xinclude/xinclude.html"> http://xw2k.sdct.itl.nist.gov/carmelo/xinclude/xinclude.html</a> </li> </ul> </dd> <p/> <dt><b>Test Archive:</b></dt> <dd><ul> <li><a href="http://xw2k.sdct.itl.nist.gov/carmelo/xinclude/xinclude0322.zip">http://xw2k.sdct.itl.nist.gov/carmelo/xinclude/xinclude0322.zip</a> </li> </ul></dd> <p/> <dt><b>W3C XML Core Working Group:</b></dt> <dd><ul><li><a href="http://www.w3.org/">http://www.w3.org/</a> </li></ul></dd> <p/> <dt><b>XML Inclusions(XInclude) Version 1.0:</b></dt> <dd><ul><li><a href="http://www.w3.org/TR/xinclude">http://www.w3.org/TR/xinclude</a> </li></ul></dd> <p/> <dt><b>Comments:</b></dt> <dd><ul><li>Sandra Martinez, NIST <a href="mailto:san...@ni..."><san...@ni...></a> </li></ul></dd> <p/> </dl> <a name="contents"/> <h2>Table of Contents</h2> <ol > <li><a href="#intro">Introduction</a></li> <li><a href="#categories">Test Case Descriptions</a></li> <li><a href="#contrib">Contributors</a></li> </ol> <a name="intro"/> <h2>1. Introduction </h2> <p> XInclude is a generic mechanism that is used to merge XML documents. XInclude uses elements, attributes and URI references which are existing XML constructs.</p> <p> Conformance tests can be used by developers, content creators, and users alike to increase their level of confidence in product quality. In circumstances where interoperability is necessary, these tests can also be used to determine that differing implementations support the same set of features. </p> <p>This report provides supporting documentation for all of the tests contributed by members of the <i>W3C</i> XML Core Working Group. Sources from which these tests have been collected include: <em> <xsl:for-each select="testcases"> <xsl:value-of select="@creator"/> <xsl:text>; </xsl:text> </xsl:for-each> </em>. It is anticipated that this report will supplement the actual tests.</p> <p>Comments/suggestions should be forwarded to <a href="mailto:www...@w3...">public XInclude comments mailing list</a>.</p> <a name="categories"/> <h2>2. Test Case Description</h2> <p> This section of this report contains descriptions of test cases, each test case includes a binary test. The test suite consists of a series of simple binary conformance tests, whereby a processor is deemed either to accept (a positive test) or reject (a negative test) the test. An expected result document is provided for the positive tests to compare the output of the processor with the reference file. Expected results are as accurate as possible, it is conceivable that a few files may diverge somewhat from the testcase description, however the idea is still captured. Negative tests are intended to identify expected errors as defined by the specification. Negative test are not accompanied by expected results.</p> <p>For an implementation to claim conformance it must pass all positive and negative tescases, which means that the implementation performed exactly as expected. </p> <p>A description for each test is presented in the following table as well as a section identifier from the Xinclude recommendation and the Colletion from which the test was originated. The test description is intended to have enough detail to evaluate diagnostic messages. Given the Test ID and the Collection, each test can be uniquely identified.</p> <xsl:apply-templates select="testcases"/> <a name="contrib"/> <h3>4. Contributors (Non-normative)</h3> <p> A team of volunteer members have participated in the development of this work. Contributions have come from: </p> <ul> <li>Sandra I. Martinez, NIST</li> <li>Daniel Veillard, Red Hat Network</li> <li>John Evdemon, FourThought</li> </ul> </body></html> </xsl:template> <xsl:template match="testcases"> <xsl:variable name="num-of-tests"> <xsl:value-of select="count(testcase)"/> </xsl:variable> <xsl:choose> <xsl:when test="$num-of-tests=0"> <table> <tr> <td bgcolor="#ffffcc">Currently there ARE NOT any tests for this test suite</td> </tr> </table> </xsl:when> <xsl:otherwise> <xsl:for-each select="testcase"> <table width="100%"> <tr valign="top"> <td width='40%'><table bgcolor='#eeeeff' border='1' width='100%'> <tr> <td width='50%'><b>Sections [Rules]:</b></td> <td bgcolor='#ffffcc'> <xsl:value-of select="section"/></td> </tr> <tr valign="top"> <td width='50%'><b>Test ID:</b></td> <td bgcolor='#ffffcc'> <xsl:variable name="test-path"><xsl:value-of select="concat(../@creator,'/',@href)"/></xsl:variable> <a href="{$root-path}{$test-path}"><xsl:value-of select="@id"/></a> </td> </tr> <tr valign="top"> <td width='50%'><b>Collection:</b></td> <td bgcolor='#ffffcc'><xsl:value-of select="../@creator"/></td> </tr> </table> </td> <td bgcolor='#ccffff'> <p><xsl:value-of select="description"/></p> <xsl:if test="output"> <p>There is an output test associated with this input file.</p> </xsl:if> </td> </tr> </table> </xsl:for-each> </xsl:otherwise> </xsl:choose> </xsl:template> <xsl:template match="EM"> <em><xsl:apply-templates/></em> </xsl:template> <xsl:template match="B"> <b><xsl:apply-templates/></b> </xsl:template> </xsl:stylesheet> --- NEW FILE: testcases.dtd --- <?xml version="1.0" encoding="UTF-8"?> <!-- @(#)testcases.dtd 04/22/02 Typical use : <DOCTYPE test-suite SYSTEM "testcases.dtd"> Purpose: To collect test cases for submission to the Xinclude Test Suite. Elements: testsuite : This is the root element of the XInclude test suite. It is a collection of testcases from various test suppliers. testcases: This element should be the root element for an individual test collection. contributor: This element can be used to name test contributors at the individual-person level. date: Date stamp on the testcase. Identifies date of creation or modification in the "qualifier" argument. testcase: An individual test in the test collection. It should provide with the following elements; description, section, contributor, date and output section: This element contains the resource argument to Point to the relevant sections in the specification. Provides a mechanism for examining the description element. Tests can apply to one or more particular SECTIONS. description: Contains the test description, used to evaluate the diagnostic produced on negative tests. People will generally read this to evaluate whether the test failed for the correct reasons (when applicable). This description will be used by the test system to be included in the tables of test cases. output: Output file (result-infoset) as expected by the submitter. This is an optional element for informational purposes only. Attributes: creator: This argument provides with the test collection originator. (tescases attribute) basedir: This argument is the base directory in which tests for this collection reside. href: Test name or reference to an individual test. id: ("test-case" attribute) Unique identifier for each test case. features: Any optional features that this test requires. Implementations not supporting a feature should skip the test. Values are: xpointer-scheme: requires the xpointer scheme unexpanded-entities: requires the parser to not expand external entities unparsed-entities: requires unparsed entity support lang-fixup: requires xml:lang fixup support qualifier: Indicates date of creation or modification of the test. resource: Pointer to the applicable section of the specification., ("section" attribute) --> <!--The root element of the whole collection is test-suite and The root element of a collection should be "testcases". --> <!ENTITY % URI "CDATA"> <!ENTITY % text "(#PCDATA | em | b | a)*"> <!ELEMENT testsuite (testcases+ )> <!ELEMENT testcases (testcase | testresult)*> <!ATTLIST testcases creator CDATA #IMPLIED basedir CDATA #IMPLIED> <!ELEMENT testcase (contributor,section+,date,description,output*)> <!ATTLIST testcase id ID #REQUIRED href %URI; #REQUIRED type (success|error|optional) #REQUIRED features NMTOKENS #IMPLIED> <!ELEMENT description (#PCDATA)> <!ELEMENT section (#PCDATA)> <!ATTLIST section resource %URI; #REQUIRED> <!ELEMENT contributor (#PCDATA)> <!ELEMENT date (#PCDATA)> <!ATTLIST date qualifier (created|modified) "created"> <!ELEMENT output (#PCDATA)> <!-- Really basic HTML font tweaks, to support highlighting some aspects of test descriptions ... EM == emphasis (e.g. italics, fun colors) B == bold --> <!ELEMENT em (#PCDATA | b)*> <!ELEMENT b (#PCDATA | em)*> <!-- We also allow for hyperlinks in text (e.g., to include references to supporting evidence within SPECPROBLEM and TESTPROBLEM). --> <!ELEMENT a (#PCDATA | b | em)*> <!ATTLIST a href %URI; #REQUIRED > <!-- The TESTRESULT element is used to record test results. It has a required ID attribute which identifies the TEST. It has a required AGREEMENT attribute that indicates whether the results are in full agreement with the expected results as described in the TEST case or not. The textual contents of the TESTRESULT element should describe the results of the test and any issues or further information. The target of the optional RESULTS attribute could be an XML Infoset The optional FUTURESUPPORT attribute is used to indicate expected future support of the feature tested by this test case. The optional SPECPROBLEM attribute indicates if there is any ambiguity or other problem found in the spec that relates to this test. Especially if the results weren't as expected because of a misinterpretation of the spec, this should be documented here. Details/discussion should appear in the textual contents of the TESTRESULT element. The optional TESTPROBLEM attribute indicates if there is any issue with the TEST case and the expected results it suggests. Especially if the results of the test differ from that given as "expected" by the test case but are, in fact, believed to be the correct results, this should be documented here. Details/discussion should appear in the textual contents of the TESTRESULT element. --> <!ELEMENT testresult %text;> <!ATTLIST testresult id CDATA #REQUIRED agreement (full|issues) #REQUIRED results %URI; #IMPLIED futuresupport (full|partial|none) #IMPLIED specproblem (yes|no) "no" testproblem (yes|no) "no" > --- NEW FILE: testdescr.xml --- <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE testsuite SYSTEM "testcases.dtd"> <testsuite> <testcases creator="Redhat" basedir="Imaq/test/XInclude/docs"> <testcase id="imaq-include-xml-01" href="include.xml" type="success"> <contributor>Daniel Veillard</contributor> <section resource="http://www.w3.org/TR/xinclude/#xml-included-items">4.2</section> <date qualifier="created">8-Mar-2002</date> <description>Simple test of including another XML document.</description> <output>../../../result/XInclude/include.xml</output> </testcase> <testcase id="imaq-include-xml-02" href="recursive.xml" type="success"> <contributor>Daniel Veillard</contributor> <section resource="http://www.w3.org/TR/xinclude/#loops">4.2.7</section> <date qualifier="created">8-Mar-2002</date> <description>Test recursive inclusion.</description> [...1554 lines suppressed...] <testcase id="harold-96" href="badelementschemedata.xml" type="success"> <contributor>Elliotte Rusty Harold</contributor> <section resource="http://www.w3.org/TR/xinclude/#include_element">3.1</section> <date qualifier="created">12-Sep-2004</date> <description>Test that a non-child sequence in an xpointer is treated as a resource error.</description> <output>../result/badelementschemedata.xml</output> </testcase> <testcase id="harold-97" href="xpointerwithpercentescape.xml" type="error"> <contributor>Elliotte Rusty Harold</contributor> <section resource="http://www.w3.org/TR/xinclude/#include_element">3.1</section> <date qualifier="created">13-Oct-2004</date> <description>Since the xpointer attribute is not a URI reference, %-escaping must not appear in the XPointer, nor is there any need for a processor to apply or reverse such escaping.</description> </testcase> </testcases> </testsuite> |
