- From: Robin Berjon <robin@berjon.com>
- Date: Mon, 16 Jan 2012 21:12:27 +0100
- To: Alan Stearns <stearns@adobe.com>
- Cc: "Linss, Peter" <peter.linss@hp.com>, public-test-infra <public-test-infra@w3.org>
On Jan 16, 2012, at 20:42 , Alan Stearns wrote:
> I wrote down what we're planning on doing for CSS Regions tests on the spec
> wiki page:
>
> http://wiki.csswg.org/spec/css3-regions#spec-and-test-metadata
>
> The main idea is that tests can link to any anchor in the spec, and
> non-testable anchors will get a new "informative" class attribute. Then the
> spec can be scanned for all non-informative anchors to discover whether
> there are corresponding tests.
This sounds similar to the process described in:
http://www.w3.org/TR/test-methodology/
Needs can vary a fair deal across groups, but overall the more we can align the more easily we can build an ecosystem of reusable tools — and it seems that spec markup ought to be reusable. The syntax used in the test meth might not be the best one but it's there, and it's been used across at least the widgets specs (and some preliminary DAP stuff). If it doesn't match your needs fully, it would probably be a good idea to figure out how to evolve it.
--
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Monday, 16 January 2012 20:13:01 UTC