Testing Policy


This text was copied from testing-how-to/#test-as-you-commit. A Working Group Charter may refer to this document. No substantive changes may be made to this document without a W3C Advisory Committee review of the Group Charters it is linked from.

Comments should be sent as a GitHub issue.

Test as you commit

All normative spec changes are generally expected to have a corresponding pull request in web-platform-tests, either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the proposed update.

Typically, both pull requests (spec updates and tests) will be merged at the same time. If a pull request for the specification is approved but the other needs more work, add the 'needs tests' label or, in web-platform-tests, the 'status:needs-spec-decision' label. Note that a test change that contradicts the specification should not be merged before the corresponding specification change.

If testing is not practical due to web-platform-tests limitations, please explain why and if appropriate file an issue with the 'type:untestable' label to follow up later.

PLH and Ralph, for the W3C Director.

Change History
Date Description
2020-06-11 Corrected typo
2019-03-24 Updated WPT repo link
2019-02-08 Text copied from testing-how-to/#test-as-you-commit

$Id: testing-policy.html,v 1.9 2020/06/11 04:30:22 clilley Exp $