- From: Alan Stearns <stearns@adobe.com>
- Date: Thu, 14 Sep 2017 22:41:55 +0000
- To: Geoffrey Sneddon <me@gsnedders.com>, public-test-infra <public-test-infra@w3.org>
Unfortunately there are two question 1s in Geoffrey’s list. I’ll refer to the second as (1). Given that there are costs associated with moving tests around, I’m slightly in favor of leaving current tests where they are. So I prefer 1a over 1b, but either of those could work for me. I don’t particularly like 1c because that creates too many top-level directories and I like having most (or all) of the CSS tests in one place. This also calls for 3b over 3a in my mind, but I think 3a could be OK if we decided on one big move and people were willing to take on the cost. A bias against moving files also makes (1)a (not using module levels in folder names) probably preferable, because we often move features back and forth between levels. We can use spec links to determine what level the test corresponds to. I don’t really care about 2, though the answer to 4 might increase the value to add new things to the css directory. On 4, I’d like to maintain the current lints on CSS, and extend them to other folders if the test suite owners would like them. I’m generally in favor of automated checks when they make sense. And keeping the spec link metadata in CSS tests is a requirement we’re going to maintain. Thanks, Alan
Received on Thursday, 14 September 2017 22:42:22 UTC