On Monday 12 March 2007 11:51, Bjoern Hoehrmann wrote:
> * Frans Englich wrote:
> >What I find the tricky part of this, is knowing when one have done it
> >correctly, and in fact have done it at all, and haven't missed anything.
> > What is the correct regression testing/quality assurance to perform on an
> > XML parser? How does one avoid ending up with junk?
> >
> >For instance, if one pass W3C's XML Test Suite[1], does that mean anything
> > in practice, or must one resort to some other kind of conformance testing
> > in addition? What do others do?
>
> If you do not pass the test suite that means something. Passing it means
> much less since no matter how many individual test cases the suite might
> have, your parser might fail to handle the one the suite does not in-
> clude. As a simple example, the suite does not have documents > 4GB in
> size. The suite is also quite incomplete, it lacks for example these:
>
>  
> http://lists.w3.org/Archives/Public/public-xml-testsuite/2005Dec/0001.html
> http://lists.w3.org/Archives/Public/public-xml-testsuite/2006Sep/0000.html

Yeah, I gave that a slight push some days ago:
http://www.nabble.com/xml:base-attributes-missing-for-eduni-tests-tf3348583.html

But with those tests or not, I'd say the coverage could be a lot more useful, 
but that applies to a lot of public test suites.


Cheers,

		Frans



_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php