W3C home > Mailing lists > Public > public-test-infra@w3.org > April to June 2012

Finding specs

From: Robin Berjon <robin@berjon.com>
Date: Mon, 4 Jun 2012 18:57:19 +0200
Message-Id: <49E87570-810E-43FC-9511-87890B2208DF@berjon.com>
To: "<public-test-infra@w3.org>" <public-test-infra@w3.org>
Hi all,

last week Dom and I went to a workshop on testing and interoperability for the Web platform in Paris. Part of the discussion was about how to get more community involvement in the production of tests. For instance: you're a web hacker, you find an interop problem between browsers, how do you get to the point where you can submit a test?

We quickly realised that the path from bug to submitted test is way too long. (Some info at http://berjon.com/presentations/20120530-mosquito-testing/mosquito-testing.html). One of the hardest steps along the way (not talking about actually writing a test in the first place) is finding which bloody group to send it to in the first place. That's relatively easy once you've found the spec  but finding the right spec is fraught with peril.

So we had an idea for a small and simple service that would map method names to specs (this is for APIs  the same idea can be generalised to CSS properties and a bunch of other things). The service would do something like:

     get list of specs from http://www.w3.org/standards/techs/js;
     extract WebIDL from those;
     parse WebIDL to extract method names, attributes, etc.;
     provide a simple search interface mapping those to their containing specs.

There are a few potential issues along the way, but overall it seems doable.

I was wondering if this is something that people here would find useful? Additionally, Dom mentioned there being some existing work along similar lines, so I'd be interested in hearing about that too.

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Monday, 4 June 2012 17:13:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 June 2012 17:13:22 GMT