[webrtc-pc] Adopt "test as you commit" policy

foolip has just created a new issue for https://github.com/w3c/webrtc-pc:

== Adopt "test as you commit" policy ==
An increasing number of groups are beginning to make web-platform-tests part of their day-to-day work, and more are considering it, for example in https://github.com/w3c/dap-charter/issues/48.

In a [Improving interop with web-platform-tests](https://bit.ly/hackfest-wpt) talk (slides 16-17 and 23) I gave here at the https://webengineshackfest.org/ I outlined the strategy, "tipping point" idea and the remaining work.

WebRTC is at the same time challenging and in an unusually good situation testing-wise. The challenge is that http://wpt.fyi/webrtc is very red because of a lack of automation. Chromium's ecosystem infra team is investing in [fixing this in Q4](https://docs.google.com/document/d/1GZquS8Jra47E5hIMH2ObOb_7oQFgk8f9MptUAjF0LFI/edit?usp=sharing) (search for "WebRTC").

What makes things better for WebRTC than most places is that testing activity is already very high (see [visualization](https://foolip.github.io/day-to-day/)) and a lot of work was done recently by @soareschen and @rwaldron to improve the test suite. See https://rwaldron.github.io/webrtc-pc/ for an an annotated version of the spec.

It could be something similar to the [SVG policy](https://github.com/w3c/svgwg/blob/master/CONTRIBUTING.md#tests), meaning:
 - Those who review spec changes ask for a corresponding PR in web-platform-tests.
 - If testing is currently impossible or impractical, issues with the type:untestable or type:missing-coverage labels are filed.
 - There are no hard rules, just a common understand of what's expected, analogous to code review practicies.


Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1617 using your GitHub account

Received on Wednesday, 4 October 2017 11:02:07 UTC