W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2017

Re: [csswg-drafts] [all] Consider policy to ask for web-platform-tests

From: Simon Pieters via GitHub <sysbot+gh@w3.org>
Date: Mon, 28 Aug 2017 10:25:14 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-325317894-1503915906-sysbot+gh@w3.org>
A few thoughts...

* I agree it would be good to document the policy in the repository, and not just have a WG resolution, to make it easier to find and to bring more confidence to the reader (a WG resolution might have been overridden later by a new WG resolution, for example).
* As for timing when it makes most sense to start writing tests for each change, I suggest it is when a feature is shipping in one or more browsers, irrespective of spec status. Experience suggests there is some lag between a feature shipping and it reaching CR, and tests are necessary i the meantime.

In particular, I think writing tests should be culturally part of day-to-day work, as an integral part of fixing spec issues. Applying it to post-CR still seems like testing can be an after-thought, after it has been specified, implemented, shipped, and web content exist that rely on implementation differences that tests were supposed to prevent.

GitHub Notification of comment by zcorpan
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1755#issuecomment-325317894 using your GitHub account
Received on Monday, 28 August 2017 10:25:13 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:17 UTC