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