- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 24 Oct 2006 03:20:12 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/test-suite
In directory hutz:/tmp/cvs-serv7033/test-suite
Modified Files:
index.html build-test-coverage.xml faq.html
Added Files:
test-suite-coverage-summary-process.html
test-suite-coverage-summary-diagram.png
test-suite-coverage-summary-diagram.vsd
Log Message:
Documented W3C WSDL 2.0 Test Suite Document Coverage Summary
Index: index.html
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/index.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -C 2 -d -r1.7 -r1.8
*** index.html 11 Jul 2006 22:26:25 -0000 1.7
--- index.html 24 Oct 2006 03:20:07 -0000 1.8
***************
*** 2,89 ****
<head>
<title>W3C WSDL 2.0 Test Suite</title>
! <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css" /></head>
<body>
<h1>W3C WSDL 2.0 Test Suite</h1>
! <address>Arthur Ryman</address>
<address>2005-02-03</address>
<h2>Introduction</h2>
! <p>
! This directory contains the W3C WSDL 2.0 Test Suite.
! The purpose of this test suite is to provide a common set of test cases that can be used by any WSDL 2.0 implementation.
! The test cases are divided into <em>good</em> and <em>bad</em> buckets.
! The good test cases are correct examples of usage.
! Our goal is to have at least one good test case for each aspect of WSDL 2.0. For example, every XML element and attribute in WSDL 2.0
! should be present in at least one good test case.
! The bad test cases are incorrect examples of usage.
! Our goal is to have at least one bad example that violates each constraint or rule in WSDL 2.0. For example, every rule that cannot be
! expressed in the XML schema for WSDL 2.0 should be violated in at least one bad document.
! </p>
! <p>
! The structure of the Test Suite is described in
! <a href="TestSuiteContents.html"><em>Test Suite Contents</em></a>.
! The test suite is contained in the following subdirectories:
! </p>
<ul>
! <li><code>document</code> contains WSDL documents</li>
! <li><code>messages</code> contains messages</li>
! <li><code>exchanges</code> contains message exchanges</li>
</ul>
<h2>Validation</h2>
! <p>
! All WSDL 2.0 documents in the test suite are required to be valid with respect to the normative XML schema for WSDL 2.0.
! There is little value in including non-valid documents, since any validating parser can check the schema rules.
! An <a href="http://ant.apache.org/">Ant</a> script is therefore provided to perform XML schema validation on all the WSDL documents.
! The <a href="http://xml.apache.org/xerces2-j/">Xerces</a> parser is used for this purpose.
! Override the Ant <code>${xercesImpl.jar}</code> property to point to where you installed Xerces on your machine.
! </p>
! <p>
! The <code>xmlcatalog</code> subdirectory contains the XML schemas for WSDL 2.0 and XSD 1.0.
! </p>
! <p>
! We are mainly concerned with test documents that violate rules that cannot be expressed in the XML schema.
! Such rules must be checked by validators, for example the Java WSDL 2.0 validator that is part of the
! Apache <a href="http://incubator.apache.org/woden">Woden</a> project
</p>
<h2>Interchange format</h2>
! <p>The Working Group has defined an XML serialization of the component model to assist in evaluating the construction
! of component models across implementation. The interchange format is defined using a
! <a href="http://dev.w3.org/cvsweb//2002/ws/desc/test-suite/interchange/">set of schemas</a> representing the
! core WSDL 2.0 component model, some base type definitions (e.g. QNames), and schemas representing each of the
extension namespaces in Part 2.</p>
! <p>Interchange results are canonicalized using a two-step process, <a href="results/canonicalize-wsdlcm.xslt">canonicalize-wsdlcm.xslt</a>
! sorts children in a canonical order, and <a href="results/canonicalize-id-wsdlcm.xslt">canonicalize-id-wsdlcm.xslt</a>
! normalizes ID and IDREF values to a canonical form. Canonicalized interchange results are compared against
! a baseline using another stylesheet (<a href="results/compare-wsdlcm.xslt">compare-wsdlcm.xslt</a>), which
! provides a summary of differences (ignoring namespace prefixes, whitespace, etc.) of the two files. These
! individual results are rolled up into an overall <a href="results/Overview.html">test result summary</a> using
! yet another stylesheet (<a href="results/combine.xslt">combine.xslt</a>) in conjunction with a list of
! <a href="results/implementations.xml">implementations</a> contributing results and the
! <a href="test-suite.xml">test-suite.xml</a> metadata.</p>
<h2>Contributing Test Cases</h2>
! <p>
! The community is encouraged to contribute test cases.
! The best way to confirm your understanding of the specification is to contribute an illustrative test case.
! Test cases should be contributed by emailing them to the W3C Web Services Description Working Group
! <a href="mailto:www-ws-desc@w3.org">mailing list</a>.
! </p>
! <p>
! This directory is stored in the <a href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/">W3C CVS repository</a>.
! CVS users are requested to email modifications or additions to the test suite as patches.
! Access CVS using the following parameters:
</p>
<ul>
! <li>host: <code>dev.w3.org</code></li>
! <li>repository path: <code>/sources/public</code></li>
! <li>connection type: <code>pserver</code></li>
! <li>user: <code>anonymous</code></li>
! <li>password: <code>anonymous</code></li>
! <li>project path: <code>/2002/ws/desc/test-suite</code></li>
</ul>
! <p>
! Contributors who are looking for a convenient, free tool to access CVS and create patches can use
! <a href="http://www.eclipse.org">Eclipse</a>.
</p>
</body>
! </html>
\ No newline at end of file
--- 2,94 ----
<head>
<title>W3C WSDL 2.0 Test Suite</title>
! <link rel="stylesheet" type="text/css"
! href="http://www.w3.org/StyleSheets/TR/base.css" />
! </head>
<body>
<h1>W3C WSDL 2.0 Test Suite</h1>
! <address><a href="mailto:ryman@ca.ibm.com">Arthur Ryman</a></address>
<address>2005-02-03</address>
<h2>Introduction</h2>
! <p>This directory contains the W3C WSDL 2.0 Test Suite. The purpose
! of this test suite is to provide a common set of test cases that can be
! used by any WSDL 2.0 implementation. The test cases are divided into <em>good</em>
! and <em>bad</em> buckets. The good test cases are correct examples of
! usage. Our goal is to have at least one good test case for each aspect
! of WSDL 2.0. For example, every XML element and attribute in WSDL 2.0
! should be present in at least one good test case. The bad test cases are
! incorrect examples of usage. Our goal is to have at least one bad
! example that violates each constraint or rule in WSDL 2.0. For example,
! every rule that cannot be expressed in the XML schema for WSDL 2.0
! should be violated in at least one bad document.</p>
! <p>The structure of the Test Suite is described in <a
! href="TestSuiteContents.html"><em>Test Suite Contents</em></a>. The
! test suite is contained in the following subdirectories:</p>
<ul>
! <li><code>document</code> contains WSDL documents</li>
! <li><code>messages</code> contains messages</li>
! <li><code>exchanges</code> contains message exchanges</li>
</ul>
<h2>Validation</h2>
! <p>All WSDL 2.0 documents in the test suite are required to be valid
! with respect to the normative XML schema for WSDL 2.0. There is little
! value in including non-valid documents, since any validating parser can
! check the schema rules. An <a href="http://ant.apache.org/">Ant</a>
! script is therefore provided to perform XML schema validation on all the
! WSDL documents. The <a href="http://xml.apache.org/xerces2-j/">Xerces</a>
! parser is used for this purpose. Override the Ant <code>${xercesImpl.jar}</code>
! property to point to where you installed Xerces on your machine.</p>
! <p>The <code>xmlcatalog</code> subdirectory contains the XML schemas
! for WSDL 2.0 and XSD 1.0.</p>
! <p>We are mainly concerned with test documents that violate rules
! that cannot be expressed in the XML schema. Such rules must be checked
! by validators, for example the Java WSDL 2.0 validator that is part of
! the Apache <a href="http://incubator.apache.org/woden">Woden</a> project
</p>
<h2>Interchange format</h2>
! <p>The Working Group has defined an XML serialization of the
! component model to assist in evaluating the construction of component
! models across implementation. The interchange format is defined using a
! <a href="http://dev.w3.org/cvsweb//2002/ws/desc/test-suite/interchange/">set
! of schemas</a> representing the core WSDL 2.0 component model, some base
! type definitions (e.g. QNames), and schemas representing each of the
extension namespaces in Part 2.</p>
! <p>Interchange results are canonicalized using a two-step process, <a
! href="results/canonicalize-wsdlcm.xslt">canonicalize-wsdlcm.xslt</a>
! sorts children in a canonical order, and <a
! href="results/canonicalize-id-wsdlcm.xslt">canonicalize-id-wsdlcm.xslt</a>
! normalizes ID and IDREF values to a canonical form. Canonicalized
! interchange results are compared against a baseline using another
! stylesheet (<a href="results/compare-wsdlcm.xslt">compare-wsdlcm.xslt</a>),
! which provides a summary of differences (ignoring namespace prefixes,
! whitespace, etc.) of the two files. These individual results are rolled
! up into an overall <a href="results/Overview.html">test result
! summary</a> using yet another stylesheet (<a href="results/combine.xslt">combine.xslt</a>)
! in conjunction with a list of <a href="results/implementations.xml">implementations</a>
! contributing results and the <a href="test-suite.xml">test-suite.xml</a>
! metadata.</p>
<h2>Contributing Test Cases</h2>
! <p>The community is encouraged to contribute test cases. The best
! way to confirm your understanding of the specification is to contribute
! an illustrative test case. Test cases should be contributed by emailing
! them to the W3C Web Services Description Working Group <a
! href="mailto:www-ws-desc@w3.org">mailing list</a>.</p>
! <p>This directory is stored in the <a
! href="http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/">W3C CVS
! repository</a>. CVS users are requested to email modifications or additions
! to the test suite as patches. Access CVS using the following parameters:
</p>
<ul>
! <li>host: <code>dev.w3.org</code></li>
! <li>repository path: <code>/sources/public</code></li>
! <li>connection type: <code>pserver</code></li>
! <li>user: <code>anonymous</code></li>
! <li>password: <code>anonymous</code></li>
! <li>project path: <code>/2002/ws/desc/test-suite</code></li>
</ul>
! <p>Contributors who are looking for a convenient, free tool to
! access CVS and create patches can use <a href="http://www.eclipse.org">Eclipse</a>.
</p>
</body>
! </html>
--- NEW FILE: test-suite-coverage-summary-diagram.png ---
(This appears to be a binary file; contents omitted.)
Index: build-test-coverage.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/build-test-coverage.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C 2 -d -r1.2 -r1.3
*** build-test-coverage.xml 19 Jul 2006 23:21:23 -0000 1.2
--- build-test-coverage.xml 24 Oct 2006 03:20:07 -0000 1.3
***************
*** 19,23 ****
<target name="reports" depends="xpaths2coverage" description="Generates coverage reports.">
-
<delete>
<fileset dir="reports/documents">
--- 19,22 ----
***************
*** 25,29 ****
</fileset>
</delete>
-
<xslt style="wsdl-coverage.xsl" basedir="documents" includes="**/*.wsdl" destdir="reports/documents" extension=".xml" force="yes" />
</target>
--- 24,27 ----
--- NEW FILE: test-suite-coverage-summary-process.html ---
<html>
<head>
<title>W3C WSDL 2.0 Test Suite Document Coverage Summary</title>
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/base.css" />
</head>
<body>
<h1>W3C WSDL 2.0 Test Suite Document Coverage Summary</h1>
<address><a href="mailto:ryman@ca.ibm.com">Arthur Ryman</a></address>
<address>2006-10-23</address>
<h2>Introduction</h2>
<p>This document describes the process for generating the <a
href="test-suite-coverage-summary.xml">WSDL 2.0 Document Test Case
Coverage Report</a>.</p>
<h2>Overview</h2>
<p>The coverage report is generated by a series of four XSLT
transformations as illustrated in the following diagram:</p>
<div align="center"><img
src="test-suite-coverage-summary-diagram.png" /></div>
<p>These transformations are invoked by the Ant build script <a
href="build-test-coverage.xml">build-test-coverage.xml</a>.</p>
<h2>Transform A: xpaths2coverage</h2>
<p>The goal of the document test suite is to ensure that each
important aspect of a WSDL 2.0 document occurs a few times. Examples of
important aspects are elements, attributes, and enumerated attribute
values. Each such aspect is described by an XPath expression that is
listed in the input data file <a href="wsdl-xpaths.xml">wsdl-xpaths.xml</a>.
The <a href="xpaths2coverage.xsl">xpaths2coverage.xsl</a> transform
converts this list into an XSLT transform, <a href="wsdl-coverage.xsl">wsdl-coverage.xsl</a>,
that counts the occurence of each XPath in an input WSDL 2.0 document.</p>
<h2>Transform B: reports</h2>
<p>The <a href="wsdl-coverage.xsl">wsdl-coverage.xsl</a> transform
is applied to each WSDL 2.0 document in the test suite and generates a
document coverage report for each document. The document coverage report
lists of the count of each XPath in the input WSDL 2.0 document. These
are stored in the reports directory and the file extension is *.xml
instead of *.wsdl.</p>
<p>This step depends on step A.</p>
<h2>Transform C: test-suite-reports</h2>
<p>The set of all WSDL 2.0 documents in the test suite is listed in
the <a href="test-suite.xml">test-suite.xml</a> data file. The <a
href="test-suite-reports.xsl">test-suite-reports.xsl</a> transform
generates a list of all the corresponding document coverage reports in
the output data file <a href="test-suite-reports.xml">test-suite-reports.xml</a>.</p>
<h2>Transform D: test-suite-coverage-summary</h2>
<p>Finally the <a href="test-suite-coverage-summary.xsl">test-suite-coverage-summary.xsl</a>
transform aggregates all the individual document coverage reports that
are listed in <a href="test-suite-reports.xml">test-suite-reports.xml</a>
into the summary coverage report <a
href="test-suite-coverage-summary.xml">test-suite-coverage-summary.xml</a>
that sums the counts of each XPath for all the documents in the test
suite. This is the default target of the build script.</p>
<p>The step depends and steps B and C.</p>
</body>
</html>
--- NEW FILE: test-suite-coverage-summary-diagram.vsd ---
(This appears to be a binary file; contents omitted.)
Index: faq.html
===================================================================
RCS file: /sources/public/2002/ws/desc/test-suite/faq.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C 2 -d -r1.3 -r1.4
*** faq.html 17 Oct 2006 16:13:51 -0000 1.3
--- faq.html 24 Oct 2006 03:20:07 -0000 1.4
***************
*** 17,20 ****
--- 17,22 ----
<li><a href="#assertion-coverage">Which bad documents should I
contribute?</a></li>
+ <li><a href="#test-suite-coverage-summary">How is the WSDL 2.0
+ Document Test Case Coverage Report produced?</a></li>
</ul>
***************
*** 131,135 ****
document is good. Optional assertions are suggestions or best practices.
They correspond to the keywords SHOULD, SHOULD NOT, and RECOMMENDED in
! the specification.
</body>
</html>
--- 133,147 ----
document is good. Optional assertions are suggestions or best practices.
They correspond to the keywords SHOULD, SHOULD NOT, and RECOMMENDED in
! the specification.</p>
!
! <h2><a name="test-suite-coverage-summary">How is the <a
! href="test-suite-coverage-summary.xml">WSDL 2.0 Document Test Case
! Coverage Report</a> produced?</a></h2>
!
! <p>The <a href="test-suite-coverage-summary.xml">report</a> is
! produced by XSLT transforms that are invoked by an Ant script. These are
! described in detail in <a
! href="test-suite-coverage-summary-process.html">W3C WSDL 2.0 Test
! Suite Document Coverage Summary</a>.
</body>
</html>
Received on Tuesday, 24 October 2006 03:20:28 UTC