Tests for WHATWG specifications are maintained in the [http://github.com/w3c/web-platform-tests web-platform-tests] repository, along with those for many other web-platform features, including all those maintained by W3C.

−

== Requirements ==

+

Tests are contributed by community members, including implementers and specification editors. Different specifications are accompanied by testsuites of varying breadth and depth.

−

* Each test needs a "reviewed" marker of some sort

+

In order to contribute tests to the testsuite for a WHATWG standard, follow the instructions on http://web-platform-tests.org/.

−

* 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

−

* If test can be done using JavaScript preferably require it to be in JavaScript so engines can be more efficiently tested (i.e. automated).

−

* It must be easy to review tests

−

* Standardize a test format?

−

== Non-requirements ==

+

== Old lists of tests that maybe have not been ported to web-platform-tests? ==

−

* 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.)

See http://omocha.w3.org/wiki/newformat for a format proposal that should meet most of these requirements. That format is based on the Mozilla Mochitest format for running JavaScript based client-side tests which can be run automatically.

+

* [https://dxr.mozilla.org/mozilla-central/search?q=file%3Areftest.list Some of Mozilla's reftests]