W3C home > Mailing lists > Public > www-style@w3.org > April 2019

Re: labels for testing

From: François REMY <francois.remy.dev@outlook.com>
Date: Thu, 25 Apr 2019 11:58:02 +0000
To: Florian Rivoal <florian@rivoal.net>, www-style list <www-style@w3.org>
Message-ID: <AM0PR0402MB3713D4B0DF0A0F5251584242A53D0@AM0PR0402MB3713.eurprd04.prod.outlook.com>
That's reasonable. Basically the idea is to have a tag to describe the end state of an issue, so it's not ambiguous. Ideally I wish GitHub had workflows to make transitions easier than adding and removing tags, but I understand the point now. Ideally, every closed issue should then be tagged with either of them (or be Closed as Invalid/No change).
________________________________
From: Florian Rivoal <florian@rivoal.net>
Sent: Thursday, April 25, 2019 9:27 AM
To: www-style list
Subject: labels for testing

Hi all,

We now have 4 labels that relate to testing on the issues in csswg-drafts, but they're not grouped together (where grouping is done by coloring and alphabetical order):

As part of the "needs edits", "needs figures", "needs feedback", we have:
* Needs testcases (WPT)
* Needs review of Test Case(s)

Separately, we also have:
* Tested
* Testing Unnecessary

Since the "Needs..." series is mostly about the spec itself, I suggest renaming the first two labels to group them with the last two:

"Needs testcases (WPT)" -> "Tests needed"
"Needs review of Test Case(s)" -> "Tests in progress, need work"

As for the color, do we want all for under a single color, or do we want to use some color contrast between the two states that indicate that nothing needs to be done and the two that indicates that something needs to be done?

—Florian
Received on Thursday, 25 April 2019 11:58:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:53:13 UTC