- From: Zhang, Zhiqiang <zhiqiang.zhang@intel.com>
- Date: Thu, 12 Sep 2013 13:37:14 +0000
- To: Rebecca Hauck <rhauck@adobe.com>, Arthur Barstow <art.barstow@nokia.com>
- CC: "public-webapps-testsuite@w3.org" <public-webapps-testsuite@w3.org>, "public-testtwf-planning@w3.org" <public-testtwf-planning@w3.org>, "'public-test-infra@w3.org'" <public-test-infra@w3.org>
+ public-test-infra@w3.org > From: Rebecca Hauck [mailto:rhauck@adobe.com] > Sent: Wednesday, September 11, 2013 6:54 AM > > On 9/9/13 6:00 AM, "Arthur Barstow" <art.barstow@nokia.com> wrote: > > >On 9/6/13 4:03 PM, ext Rebecca Hauck wrote: > >> As you might imagine though, it wouldn't be realistic to > >> expect newcomers to jump into that. > > > >I agree it could be challenging. OTOH, perhaps it could be useful to > >make "reviewing some set of `approved` tests" a prerequisite for > >submitting new tests ;-). > > We definitely do that. In fact, we usually ask the experts to provide > starter tests that serve as good examples upon which new authors can build > new tests. These starter tests are almost always actual tests that have > been approved. Of course, the difference here is that they're reviewing > tests as a learning mechanism vs. reviewing them to bless them for all. > I'm fairly certain we wouldn't expect (or want) newcomers to be > responsible for the latter. I wonder if it is possible to add a topic, How to Review a Test, at the event. This will not only benefit new reviewers to understand the review process, but help new authors to know about what is to be checked before submitting new tests. Before that, shall we come to a recommended and practical review process starting from the Test Review and Approval Process [1] and the Test Review Checklist [2]? [1] https://github.com/w3c/testtwf-website/blob/gh-pages/docs/review-process.md [2] https://github.com/w3c/testtwf-website/blob/gh-pages/docs/review-checklist.md
Received on Thursday, 12 September 2013 13:37:46 UTC