Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] AltovaXML bugs? (and other engines)

From: Michael Ludwig <mlu@------------->
To:
Date: 4/1/2009 9:53:00 AM
Michael Kay schrieb:
Unfortunately the W3C test suite is available to members only,
largely because there is not complete traceability of the origin
of all the tests.


From: Scott Trenda [mailto:Scott.Trenda@xxxxxxxx]


Just a thought (maybe someone's done it already)... is there
some sort of Acid test for XSLT processors? I think there are
conformance test packages available from W3C, but it's
usually the experienced XSLT developers who know how best to
break an XSLT engine. It'd be nice to have such a test for
both XSLT 1.0 and XSLT 2.0, since we could know exactly how
and where the different XSLT engines fail.

I agree a publicly available test suite for both XSLT 1.0 and 2.0
would be an excellent facility.

Is there an established standard or pattern or best practice for
coding tests? A framework you would just drop a new test in so it
becomes part of the test suite?

Maybe the W3C has come up with such a framework and is willing to
make it a public resource for the advancement of the Good Cause
while continuing, of course, to withhold the test suite due to its
partly shady, or intraceable, origins?

Michael Ludwig


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent