Re: Agenda+ Testing links in the spec; spec test coverage analysis

Oh, this is kind of cool.  And by default, the tests don't display in the
rendered doc, so it won't affect the output.

Therefore, I don't think we need to stop publication for this, and we can
add it in whenever we want since it doesn't affect output.


On Thu, May 30, 2019 at 6:17 AM Chris Lilley <chris@w3.org> wrote:

> Caveat: This is new, so I can appreciate we might not want to be test
> pilots here
> Caveat: this is not a requirement for publishing an updated CR
>
> Bikeshed has a (long time coming but fairly) new and (currently) not much
> used feature where a <wpt> element can be inserted in a spec (roughly at
> the paragraph level) to link out to a WPT test. That lets people reading a
> sec see immediately which parts are well tested and which are not.
>
> rationale:
>     https://github.com/tabatkins/bikeshed/issues/1116
>
> documentation:
>     https://tabatkins.github.io/bikeshed/#testing
>
> other issues:
>     https://github.com/tabatkins/bikeshed/issues/1288
>     https://github.com/tabatkins/bikeshed/issues/1263
>
> Do we want to
>
> a) do this to the spec *before *publishing an updated CR
>
> b) do this at some later time, in a different update
>
> c) skip this and concentrate on Web Audio API 2.0
>
> (these are all reasonable answers, this isn't a trick question)
>
> --
> Chris Lilley
> @svgeesus
> Technical Director @ W3C
> W3C Strategy Team, Core Web Design
> W3C Architecture & Technology Team, Core Web & Media
>
>