- From: Aryeh Gregor <ayg@aryeh.name>
- Date: Tue, 17 Jan 2012 12:00:14 -0500
- To: Arthur Barstow <art.barstow@nokia.com>, public-webapps-testsuite@w3.org
- Cc: Anne van Kesteren <annevk@opera.com>, Ms2ger <ms2ger@gmail.com>
Currently there are a number of DOM4 tests (primarily Range-related) that are undergoing active revision. The tests are fairly complicated, and bugs tend to crop up, e.g.: https://www.w3.org/Bugs/Public/show_bug.cgi?id=15583 https://www.w3.org/Bugs/Public/show_bug.cgi?id=15584 Also, I'm expanding and revising some of the tests on an ongoing basis. Previously we had a Request for Review of a bunch of submitted tests, which had zero responses: http://lists.w3.org/Archives/Public/public-webapps-testsuite/2011Nov/0008.html I suspect that zero responses will be typical for such RfRs. Bugs will be found as implementers actually try to pass all the tests, as Opera has been doing recently. On the other hand, having to wait for an RfR before approving test changes is cumbersome. Thus I suggest that for DOM4, tests can be moved to the approved/ directory by any DOM4 editor at their discretion, the same as the spec itself can be changed. The tests can be reviewed and approved by the Working Group at a later date, at the same time as the spec itself. When the spec becomes finalized at the PR stage, the tests can be finalized too, or at least stabilized (with changes requiring WG approval). But for now they should just be maintained by the editors, like the spec. Does anyone object to this? If not, I'll update Status.html.
Received on Tuesday, 17 January 2012 17:01:09 UTC