Testing

This document contains some general and historical information about WebApps' testing effort.

See WebApps' GitHub Testing wiki for information about how to Submit a test, the test case review and approval workflow, etc.

Comments on this document are welcome and should be submitted to the WG's public-webapps-testsuite e-mail list (archive).

Goals of the Testing Process

The high-level goals for the WG's testing efforts include:

Use a light-weight, asynchronous participation model that is consistent with the WG's WorkMode practices
Use explicit Calls for Consensus (CfC) to determine the level of support for specific questions, issues etc. (For instance, a CfC to Approve test cases X, Y and Z for spec A)
Each spec should have its own test suite
Test suites should use a consistent directory structure and consistent processes (e.g. submission and approval)
It should be possible for a test suite to re-use part(s) of another test suite
Test suites should use processes that are consistent (as much as possible) with other closely related WGs such as the HTML WG
The status of a test suite (e.g. all tests formally Approved by the WG, test cases A,B,C approved by WebApps' testing group, no test cases approved, etc.) should be clear

The WG uses GitHub as described in WebApps' GitHub Testing wiki.

The test Submission and Approval workflows are described in WebApp's GitHub Testing wiki.

public-webapps-testsuite@w3.org - WebApps' testing mail list used to discuss test cases, announce new test contributions, announce CfCs to review and approve tests, etc.

Testing Infrastructure Requirements; defines the requirements for the WG's testing infrastructure