- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Mar 2023 20:26:29 +0000
- To: public-css-archive@w3.org
> Would it be appropriate to get a WG resolution on this, effectively approving that WPT drops support for the old CSS build system requirements? @foolip Can you define what this means exactly? > Some of the historical needs for the harness were for tracking fully manual and reference tests, I don't know how/if WPT deals with those these days or if they're still relevant. IIRC, manual tests aren't managed in any way in WPT, and it's a problem for testing some of our features. I don't buy Tab's argument that the tests are likely broken because they haven't been run; they're much more likely still relevant. And we need *more* such tests, not fewer. There are a lot of platform features that aren't properly tested in WPT *because* they're unreasonable to automate. @plinss What information is the test harness ingesting from the build system? If it's a manifest file of some kind, we could build an indexer that doesn't actually build the tests (which I agree is a step we no longer need). -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6896#issuecomment-1481849800 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 March 2023 20:26:31 UTC