1## Test Review Policy 2 3In order to encourage a high level of quality in the W3C test 4suites, test contributions must be reviewed by a peer. 5 6The reviewer can be anyone (other than the original test author) that 7has the required experience with both the spec under test and with the 8test [format][format] and [style][style] guidelines. Review must 9happen in public, but the exact review location is flexible. In 10particular if a vendor is submitting tests that have already been 11reviewed in their own review system, that review may be carried 12forward, as long as the original review is clearly linked in the 13GitHub pull request. 14 15To assist with test reviews, a [review checklist][review-checklist] 16is available. 17 18## Review Tools 19 20All new code submissions must use the GitHub pull request 21workflow. The GitHub UI for code review may be used, but other tools 22may also be used as long as the review is clearly linked. 23 24## Labels 25 26Pull requests get automatically labelled in the GitHub repository. Check 27out the [list of labels in Github][issues] 28to see the open pull requests for a given specification or a given Working Group. 29 30## Status 31 32The 33[web-platform-tests dashboard](http://testthewebforward.org/dashboard/#all) 34shows the number of open review requests, and can be filtered by testsuite. 35 36[format]: ./test-format-guidelines.html 37[style]: ./test-style-guidelines.html 38[review-checklist]: ./review-checklist.html 39[issues]: https://github.com/w3c/web-platform-tests/issues 40