W3C home > Mailing lists > Public > public-css-testsuite@w3.org > April 2017

[OFFLIST] Re: Guidelines for editing the CSS testsuite with github

From: Gérard Talbot <css21testsuite@gtalbot.org>
Date: Wed, 12 Apr 2017 17:23:43 -0400
To: Geoffrey Sneddon <me@gsnedders.com>
Cc: Chris Lilley <chris@w3.org>, Thierry MICHEL <tmichel@w3.org>, Public CSS Test suite mailing list <public-css-testsuite@w3.org>
Message-ID: <1f7cf28ebe195a31c02a2c1afda8b2de@gtalbot.org>
Le 2017-04-12 12:36, Geoffrey Sneddon a écrit :

> I know some of documentation is wrong, but all of it was
> wrong before the merge and merging it hasn't made it any more wrong,

I agree with you on this. But I want to add that, in my humble opinion, 
fixing and/or updating accordingly all documentations should be a 
priority. Especially if new procedures, new norms are in place now.

> I don't think it's reasonable to expect me to fix all the problems
> with documentation around the testsuite.

Who is responsible for problems with documentation around testsuites, 
test management, etc... I am not trying to, not looking to blame anyone 
here. I really wish we (test authors, test reviewers) could have 
reliable (as reliable as humanly possible), trustworthy (as trustworthy 
as humanly possible) documentation around testsuites, test management at 
all time.

Writing Tests

General Test Guidelines

Test Review Checklist

Test Templates

Writing Reftests
Received on Wednesday, 12 April 2017 21:24:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 12 April 2017 21:24:22 UTC