- Each test needs a "reviewed" marker of some sort
- It must be easy to find tests where the spec has changed under them
- The barrier to contribution must be as low as possible
- Testcases should have somewhat stable URIs
- It must be easy to review tests
- Tests and test suites must be liberally licensed (e.g. PD/CC0, BSD, MIT)
- Standardize a test format?
How to license your test suite
Put your test suite into the Public Domain using the Creative Commons CC0 1.0 Public Domain Dedication.
Example markup you can include in the test suite. Either one is sufficient. The visible one is preferred.
Visible (e.g. in a visible header/footer on the test suite home page):
This test suite is placed into the <a rel="license" href="http://creativecommons.org/publicdomain/zero/1.0/"> public domain using CC0 </a>.
Invisible (e.g. inside the <head> element on the test suite home page):
<link rel="license" href="http://creativecommons.org/publicdomain/zero/1.0/" title="This test suite is placed into the public domain using CC0." />
- There does not need to be a single consistent test harness for the whole of HTML5. (When sections can be tested in isolation, each section should use a test harness that is suited to that section's testing requirements. E.g. there is little value in fitting canvas tests and parser tests into the same framework, and it may add a lot of complexity.)
- Test cases
- The specification has links to test in the status boxes.
- IE's tests
- Opera's tests
- (Some of?) WebKit's tests
- Some of Mozilla's mochitests
- Some of Mozilla's reftests
- Philip's canvas tests
- Hixie's ad-hoc tests
- Lachlan's tests
- gsnedders' number parsing tests
- zcorpan's tests
- Mathias’s tests
- html5lib tests
- hsivonen's video tests
- Document Object Model (DOM) Conformance Test Suites
- Window test suite