W3C home > Mailing lists > Public > www-dom-ts@w3.org > May 2004

Re: DOM TS svg tests

From: Curt Arnold <carnold@houston.rr.com>
Date: Wed, 5 May 2004 15:04:51 -0500
Message-Id: <77B739D3-9ECF-11D8-9AF0-000393B97126@houston.rr.com>
Cc: www-dom-ts@w3.org
To: Rob Buis <rwlbuis@xs4all.nl>

The self-hosted in SVG stuff is definitely experimental and I would 
appreciate problem reports.  I have been able to run individual tests 
in Batik but only able to run in Adobe SVG after manually hacking to 
add the test framework into the test document instead of using an 
entity reference.  Because of the manual nature of running the 
self-hosted tests, I have not attempted to run all the tests and expect 
that there are some failures due to framework or production problems.  
With KSVG's integration with Konqueror, I assume that you are able to 
browse to the test directory and see a whole bunch of green and red 

Any test that depends on the total count of elements in the document 
has a high likelihood of problems since the self-hosted tests depend on 
inserting script elements into the document that don't appear in the 
documents for the additional test suite.

Tests that load more than one document (typically to try to induce 
WRONG_DOCUMENT_ERR's or the like) are problematic for the self-hosted 
tests.  If the document URL's were identical, the documents returned on 
the subsequent calls to load were clones of the initial document.  If 
the URL's don't match, then the tests should be skipped.

The Bugzilla for the DOM TS should be used to log problems with the 
test suite or the productions (http://www.w3.org/Bugs/Public).  I 
haven't seen any traffic on the TS mailing list for quite a while, but 
I haven't send anything myself.  If this doesn't hit the mailing list, 
I'll follow up with the W3C staff.

On May 5, 2004, at 2:31 PM, Rob Buis wrote:

> Hi Curt,
> We started verifying our dom implementation against the dom ts 
> testsuites. We are starting
> with the dom core 1/2/3 test svg files, but are intending of also 
> testing event implementation etc.
> The progress has been quite good recently. However there are a few 
> testcases and constructions in the dom1 and
> dom2 core set that we are not sure are 100% correct. For instance I do 
> not understand how the multiple document
> loading works, and I think maybe in the translation from xml to svg 
> tests some things (like counting the number of
> elements) go wrong. Please note that this is no criticism, it is quite 
> possible our implementation is just wrong in
> these cases, but I just want to clear up these issues.
> Is there a good way we can discuss some testcases? I tried mailing the 
> dom-ts mailing list (twice) but it seems down?
> BTW thanks for the work on the overall high-quality testcases!
> Cheers,
> Rob.
Received on Wednesday, 5 May 2004 16:04:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:06 UTC