- From: Philip Jägenstedt <web-platform-tests-notifications@w3.org>
- Date: Tue, 11 Apr 2017 17:10:23 GMT
- To: public-web-platform-tests-notifications@w3.org
Pedantic clarity much appreciated, thanks @plinss! The way I see things is that the group of people doing the spec+implementation work should also have ownership of and responsibility for the testsuite, and get to decide on matters like this. That group does not include me. My interest is only to make it clear where to write new tests, for people working on Blink. Regarding getting things to REC, you're right that plenty of wpt contributors, including me, don't place much value on that, and are skeptical about spec levels and the resulting -n suffixes. But any time that there's a difference in opinion about how a spec's test suite should look, again I think that the people doing the work should get to decide. This quarter, @jeffcarp and @qyearsley are working on https://wptdashboard.appspot.com/ which I think will be very useful for finding and prioritizing interop problems, and incidentally also getting things to REC. The data isn't updated frequently yet, but there's something already: https://wptdashboard.appspot.com/t/cssom https://wptdashboard.appspot.com/t/cssom-view However, we (Google) can't make guarantees about when that will be ready, and I didn't have it in mind when making this change. It'll still be awesome though :) Concretely, we now have two options: 1. Leave all tests in cssom/ and cssom-view/ 1. Move them all to css/cssom-1/ and css/cssom-view-1/ Would it still be useful to ask www-style at this point? View on GitHub: https://github.com/w3c/web-platform-tests/pull/5269#issuecomment-293331918
Received on Tuesday, 11 April 2017 17:10:35 UTC