- From: Matt Womer <mdw@w3.org>
- Date: Tue, 25 Sep 2012 07:58:24 -0400
- To: public-geolocation@w3.org
Hi all, The Geolocation API has been a Proposed Recommendation for some time now. I've been in discussion with the management about how to move forward to full Recommendation status. It was expected by the time Geolocation was ready to go to Recommendation that WebIDL would have progressed significantly through the process. Since that hasn't happened, we've come up with an alternative. In essence, we will need to write tests that ensure implementations work as dictated by the WebIDL we've written. For example, are members marked readonly truly readonly? I've started on this process and would like some help from the working group. I began working with idlharness.js [1] hoping to use it to parse the WebIDL into something we could use to compare to the actual JavaScript objects we have in a generic way. There were a few gotchas, and I never quite got it working. This could be a nice generic and automated way of testing any spec that uses WebIDL and JavaScript. But, after wrestling with that for a while, I started writing tests by hand. I tested for some of the obvious things (types, readonly, etc), and some less obvious things (IDL makes requirements on the value of toString operations on classes for example, something I would never have caught without looking at the WebIDL spec). Of the less obvious things there may be a significant number that will require a someone to dive deep into the IDL spec and make sure we test them all. The obvious things just require some tedium of writing the tests. We should collaborate with the WebIDL folks in the WebApps WG as well if we have questions about the spec or how to test it. When we can show we have implementations that work as dictated by the WebIDL we should be able to get the Director's blessing to move to Recommendation. I've started seeding some tests here: http://dev.w3.org/geo/api/idl-test-suite/ It could probably use some reorganization/rewriting, but as an example of the tests we need it should serve fine. It uses testharness.js [2], which I suggest looking at before adding tests. Feel free to contribute any ideas here on the list or directly into the test file itself. -Matt Womer [1] http://w3c-test.org/resources/idlharness.js [2] http://w3c-test.org/resources/
Received on Tuesday, 25 September 2012 11:58:50 UTC