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
m (no longer current URL)
(Update testsuite page, fix redirecting links)
 
(9 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Requirements ==
+
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.
  
* Each test needs a "reviewed" marker of some sort
+
Tests are contributed by community members, including implementers and specification editors. Different specifications are accompanied by testsuites of varying breadth and depth.
* 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 ==
+
In order to contribute tests to the testsuite for a WHATWG standard, follow the instructions on http://web-platform-tests.org/.
  
* 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.)
+
== Old lists of tests that maybe have not been ported to web-platform-tests? ==
  
== Format proposal ==
+
People should prune this list...
  
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://trac.webkit.org/browser/trunk/LayoutTests (Some of?) WebKit's tests]
 
+
* [[Testsuite/Mozilla]]
== Existing tests ==
+
* [https://dxr.mozilla.org/mozilla-central/search?q=file%3Areftest.list Some of Mozilla's reftests]
* [[Test cases]]
+
* [https://philip.html5.org/tests/canvas/suite/tests/ Philip's canvas tests]
* [http://www.whatwg.org/html5 The specification] has links to test in the status boxes.
 
* [http://samples.msdn.microsoft.com/ietestcenter/ IE's tests]
 
* [http://tc.labs.opera.com/html/ Opera's tests]
 
* [http://trac.webkit.org/browser/trunk/LayoutTests (Some of?) WebKit's tests]
 
* [http://mxr.mozilla.org/mozilla-central/find?string=test_.*%28html|svg%29%24&tree=mozilla-central&hint= Some of Mozilla's mochitests]
 
** [[Testsuite/Mozilla]]
 
* [http://mxr.mozilla.org/mozilla-central/find?string=reftest.list Some of Mozilla's reftests]
 
* [http://philip.html5.org/tests/canvas/suite/tests/ Philip's canvas tests]
 
 
* [http://hixie.ch/tests/adhoc/html/ Hixie's ad-hoc tests]
 
* [http://hixie.ch/tests/adhoc/html/ Hixie's ad-hoc tests]
 
* [http://lachy.id.au/dev/markup/tests/html5/ Lachlan's tests]
 
* [http://lachy.id.au/dev/markup/tests/html5/ Lachlan's tests]
* [http://hg.gsnedders.com/php-html-5-direct/file/tip/tests/numbersTest gsnedders' number parsing tests]
+
* [https://bitbucket.org/gsnedders/php-html-5-direct/src/8c27462f5f410319011f30ce7151ed1d6f17b800/tests/numbersTest?at=default&fileviewer=file-view-default gsnedders' number parsing tests]
* [http://simon.html5.org/test/html/ zcorpan's tests]
+
* [https://simon.html5.org/test/html/ zcorpan's tests]
* [http://mathias.html5.org/tests/ Mathias’s tests]
+
* [https://hasather.net/test/html/ David Håsäther's tests]
* [http://code.google.com/p/html5lib/source/browse/testdata html5lib tests]
+
* [https://mathias.html5.org/tests/ Mathias’s tests]
* [http://hsivonen.iki.fi/test/moz/video-selection/ hsivonen's video tests]
+
* [https://hsivonen.com/test/moz/video-selection/ hsivonen's video tests]
* [http://www.w3.org/DOM/Test/ Document Object Model (DOM) Conformance Test Suites]
+
* [https://www.w3.org/DOM/Test/ Document Object Model (DOM) Conformance Test Suites]
* [http://dev.w3.org/2006/webapi/WindowTestSuite/ Window test suite]
+
* <del>[https://dev.w3.org/cvsweb/2006/webapi/WindowTestSuite/ Window test suite]</del> all checked and submitted ―[[User:Ms2ger|Ms2ger]] ([[User talk:Ms2ger|talk]]) 16:17, 29 February 2016 (UTC)
 
 
=== W3C ===
 
* [http://dev.w3.org/geo/api/test-suite/ Geolocation]
 
* [http://dvcs.w3.org/hg/webapps WebApps WG]
 
* [http://dvcs.w3.org/hg/html HTML WG]
 
* [http://hg.csswg.org/test CSS WG]
 

Latest revision as of 12:34, 24 August 2017

Tests for WHATWG specifications are maintained in the web-platform-tests repository, along with those for many other web-platform features, including all those maintained by W3C.

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

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

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

People should prune this list...