W3C home > Mailing lists > Public > public-css-testsuite@w3.org > September 2008

Re: Test Review Process Revision

From: fantasai <fantasai.lists@inkedblade.net>
Date: Fri, 26 Sep 2008 15:00:58 -0700
Message-ID: <48DD5B9A.8050107@inkedblade.net>
To: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>

Melinda asked for another change in the review process to make it more efficient,
specifically, allowing the reviewer to directly make the changes necessary for
the test to pass review. I've updated the guidelines to say the following:

   If the test does not pass review, the reviewer must tell the submitter what
   is wrong with the test and what steps should be taken to correct any problems.
   Typically the submitter is responsible for fixing the tests, but if the reviewer
   has permission (or the tests have been abandoned) s/he may make the changes
   directly and then explain to the submitter what they were and why they were
   necessary. In this case the submitter (or, in the case of abandoned tests,
   another reviewer) needs to review and accept these changes.

This keeps the requirement that all changes made by one person need to be reviewed
by another person, in this cases the reviewer and the submitter switch roles. It
also makes sure that the submitter understands what the problems were so s/he can
learn to make better tests the next time around.

~fantasai
Received on Friday, 26 September 2008 22:01:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 September 2010 17:51:57 GMT