Problem: while CSSWG drafts link to their test suites, it is far too hard to figure out how to review & report problems with existing tests, and how to contribute new tests. We need usable test suite documentation, and should consider at a minimum having our specs directly link to where to file test suite issues.
The WG wiki page on tests is horribly out of date, as are nearly all its subpages. And links to the "Web Platform Tests" site land you at pages so opaque that it is unclear if you’ll have to guess correctly and click 3 or 30 nested links to find out where to give feedback or contribute tests. I made some bandaid fixes to that WG wiki test page with a direct link to issues and also to Rachel Andrew's excellent post Christmas Gifts for Your Future Self: Testing the Web Platform, but that wiki page as a whole needs to be completely rethought and rewritten.
Since having valid (reviewed) tests for a feature is required for that feature to exit CR, and missing such tests (or being unsure of them) is often something that blocks CSSWG drafts from progressing, this issue should remain open here (perhaps as a meta issue) until sufficient solutions are found / deployed that demonstrate increased feedback and contributions to test suites for CSSWG specifications. (When people wonder why aren’t more web developers contributing or giving feedback on CSS tests, the poor usability barriers of these docs alone are a likely sufficient explanation, and thus a good place to start fixing.)
This issue directly affects all current CSSWG drafts at CR or earlier stages that are being developed in this repo and which we want to eventually (preferably efficiently) advance to PR. Thus please leave this issue open here in this repo for the CSS Working Group to resolve (rather than say, attempting to lump it or transfer it into some broader "Web Platform Tests" issue). Some more background: issue 2378
cc: @gsnedders @liamquin @atanassov @astearns