At the last F2F, we've agreed to require tests (or a good explanation of why you cannot) for all changes to specs ≥ CR. Before that, tests are recommended but not mandatory, to avoid test churn and work overload on know-to-be unstable specs or sections. The wording you're proposing in that PR seems compatible with that approach. Minutes here: https://logs.csswg.org/irc.w3.org/css/2017-08-03/#e843981 (The "Automating Test Coverage" topic title is inacurate: two topics got blended in one) Do you think we need anything else? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1755#issuecomment-324450280 using your GitHub accountReceived on Wednesday, 23 August 2017 20:18:11 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:17 UTC