A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "Testsuite"

From WHATWG Wiki
Jump to: navigation, search
(W3C: +w3c/web-platform-tests)
(Update to mitigate some confusion per https://groups.google.com/a/chromium.org/d/msg/blink-dev/jRzvehX9U1U/BCEpUwnLAwAJ)
Line 1: Line 1:
== Requirements ==
+
== Web Platform Tests ==
  
* Each test needs a "reviewed" marker of some sort
+
The [web platform tests](https://github.com/w3c/web-platform-tests) project is the shared space for testing all web platform features. It is under the "w3c" GitHub organization, but is not exclusive to W3C specs, or [[specs that have been copy-and-pasted into w3.org|fork tracking]]. Tests for WHATWG specifications should be contributed there.
* 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
 
* Tests and test suites must be liberally licensed (e.g. PD/CC0, BSD, MIT)
 
* Standardize a test format?
 
  
== How to license your test suite ==
+
For more information on web platform testing, see http://testthewebforward.org/docs/.
  
Put your test suite into the Public Domain using the [http://creativecommons.org/publicdomain/zero/1.0/ 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.
+
== Old lists of tests that maybe have not been ported to web platform tests? ==
  
Visible (e.g. in a visible header/footer on the test suite home page):
+
People should prune this list...
<pre><nowiki>
 
This test suite is placed into the
 
<a rel="license"
 
  href="http://creativecommons.org/publicdomain/zero/1.0/">
 
public domain using CC0
 
</a>.
 
</nowiki></pre>
 
  
Invisible (e.g. inside the &lt;head&gt; element on the test suite home page):
 
<pre><nowiki>
 
<link rel="license"
 
      href="http://creativecommons.org/publicdomain/zero/1.0/"
 
      title="This test suite is placed into the public domain using CC0." />
 
</nowiki></pre>
 
 
== Non-requirements ==
 
 
* 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.)
 
 
== Format proposal ==
 
 
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.
 
 
== Existing tests ==
 
 
* [[Test cases]]
 
* [[Test cases]]
 
* [http://www.whatwg.org/html5 The specification] has links to test in the status boxes.
 
* [http://www.whatwg.org/html5 The specification] has links to test in the status boxes.

Revision as of 23:35, 17 January 2016

Web Platform Tests

The [web platform tests](https://github.com/w3c/web-platform-tests) project is the shared space for testing all web platform features. It is under the "w3c" GitHub organization, but is not exclusive to W3C specs, or fork tracking. Tests for WHATWG specifications should be contributed there.

For more information on web platform testing, see http://testthewebforward.org/docs/.


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

People should prune this list...

W3C