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.
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 example a CfC could be used to approve a set of tests used to qualify a Candidate Recommendation.)
- 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 should be clear (e.g. which tests formally Approved by the WG to qualify a Candidate Recommendation)
The WG uses GitHub as described in WebApps' GitHub Testing wiki.
WebApps Testing Resources
- The test Submission and Approval workflows are described in WebApp's GitHub Testing wiki.
- Harness - describes the test harness used by the test suites
email@example.com- WebApps' primary mail list is used to discuss test cases, announce new test contributions, etc.
- Testing Infrastructure Requirements; defines the requirements for the WG's testing infrastructure
Other Testing Resources at the W3C
- Policies for Contribution of Test Cases to W3C
- Licenses for W3C Test Suites
- Test Development FAQ
- W3C Quality Assurance Library
- Inventory of W3C Test Suites; aka "The QA Matrix"
- Requirements for HTML Testing Harnerss; by James Graham 20-Apr-2010
- Reference Tests (aka RefTests): see RefTests by the CSS WG and Creating reftest-based unit tests by Mozilla