W3C home > Mailing lists > Public > public-webapps-testsuite@w3.org > October 2011

Fwd: New tests for element traversal properties

From: Arthur Barstow <art.barstow@nokia.com>
Date: Wed, 05 Oct 2011 14:16:46 -0400
Message-ID: <4E8C9F0E.10909@nokia.com>
To: public-webapps-testsuite@w3.org
CC: Philippe Le Hégaret <plh@w3.org>
-------- Original Message --------
Subject: 	New tests for element traversal properties
Resent-Date: 	Wed, 5 Oct 2011 18:04:53 +0000
Resent-From: 	<public-webapps@w3.org>
Date: 	Wed, 5 Oct 2011 14:04:44 -0400
From: 	ext Philippe Le Hegaret <plh@w3.org>
Organization: 	World Wide Web Consortium
To: 	public-webapps <public-webapps@w3.org>

I took a pass at rewriting the existing element traversal tests we have
at [1]:

The new tests now relies on testharness.js, so they can easily be
integrated in the framework.

I also submitted those tests to DOM Core as well:

As long as DOM Core does not modify the properties from what is defined
in Element Traversal, I'll keep them in sync. If they diverge, then I'll
only do bug fixes for the Element Traversal ones and will involve the
DOM Core tests instead.

Feedback is welcome of course.

The tests are not ready for approval yet because the new tests are going
beyond what the existing tests were doing:
- the new tests are trying to check if the properties are effectively
read only and there are questions around the assert_readonly function.
- the new tests are doing more on testing the dynamic aspects of the
properties, thus reporting more failures in existing implementations
(unless I got the tests wrong of course).

So, at least until the assert_readonly issue settles down, I don't plan
to ask for those tests to be approved.

In the meantime, I'm more than happy to get feedback and bug reports,


[1] http://w3c-test.org/webapps/ElementTraversal/tests/approved/
Received on Wednesday, 5 October 2011 18:17:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:57:39 UTC