W3C home > Mailing lists > Public > www-dom-ts@w3.org > December 2003

Some LS test-issues

From: Sander Bos <sander@x-hive.com>
Date: Sun, 28 Dec 2003 22:56:40 +0100
Message-ID: <001601c3cd8d$7952faf0$9600000a@mycomp>
To: <www-dom-ts@w3.org>


Hi there,

here are some more issues with tests that I found. Sorry if they are
duplicates, but I figured the CVS version of saturday that I used would have
most reported issues removed (plus, it should be easy enough to ignore
them....):

files/test7.xml:
  has reference to files/text5.xml in it, but that one is in the same
directory, and named differently (test5.xml).
DOMImplementationLSTest1
  Should be optional test, should test for LS-ASync support before creating
parser?
DOMInputSourceTest3
  resource resolver should not give back null result, then parser will look
for 'new_system' file on filesystem.
DOMInputSourceTest6
  <characterStream obj="inputSource" var="myReader" interface="LSInput"/>
  in Java becomes
  myReader = inputSource.getCharacterStream();
  so stream is not set on input (input is empty).
DOMWriterFilterTest0:
  <getAttribute var="attr1" obj="elt1" name='"attr1"'/>
discovered during implementation that this does not test whether the whole
attribute is 'accidentally'
removed (getAttribute returns empty string for non-existing attributes).
Since I think most impls are likely to get this wrong at first may be idea
to add extra check that attr1 is present (but empty), also to distinguish it
from next test.
DOMWriterFilterTest1:
  The check at the end should verify that the attribute is now gone, not
that it is still there as it does now.
SystemId1/SystemId2:
  Parser should be made synchronous, not constant 0. Elena reported that
these tests were wrong in other ways but they are running for me now (so
maybe our impl does the wrong thing there?).

Kind regards,

--Sander.
Received on Sunday, 28 December 2003 16:55:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:49 GMT