<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.whatwg.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Maria</id>
	<title>WHATWG Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.whatwg.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Maria"/>
	<link rel="alternate" type="text/html" href="https://wiki.whatwg.org/wiki/Special:Contributions/Maria"/>
	<updated>2026-04-29T11:34:07Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.3</generator>
	<entry>
		<id>https://wiki.whatwg.org/index.php?title=Testsuite&amp;diff=5089</id>
		<title>Testsuite</title>
		<link rel="alternate" type="text/html" href="https://wiki.whatwg.org/index.php?title=Testsuite&amp;diff=5089"/>
		<updated>2010-07-19T06:32:41Z</updated>

		<summary type="html">&lt;p&gt;Maria: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Existing tests URI: http://dev.w3.org/html5/tests/&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.superiorpapers.com/ custom research paper]&lt;br /&gt;
* Each test needs a &amp;quot;reviewed&amp;quot; marker of some sort&lt;br /&gt;
* It must be easy to find tests where the spec has changed under them&lt;br /&gt;
* The barrier to contribution must be as low as possible&lt;br /&gt;
* Testcases should have somewhat stable URIs&lt;br /&gt;
* If test can be done using JavaScript preferably require it to be in JavaScript so engines can be more efficiently tested (i.e. automated).&lt;br /&gt;
* It must be easy to review tests&lt;br /&gt;
* Standardize a test format?&lt;br /&gt;
&lt;br /&gt;
== Non-requirements ==&lt;br /&gt;
&lt;br /&gt;
* 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&#039;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.)&lt;br /&gt;
&lt;br /&gt;
== Format proposal ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Existing tests ==&lt;br /&gt;
* [[Test cases]]&lt;br /&gt;
* [http://www.whatwg.org/html5 The specification] has links to test in the status boxes.&lt;br /&gt;
* [http://samples.msdn.microsoft.com/ietestcenter/ IE&#039;s tests]&lt;br /&gt;
* [http://tc.labs.opera.com/html/ Opera&#039;s tests]&lt;br /&gt;
* [http://trac.webkit.org/browser/trunk/LayoutTests (Some of?) WebKit&#039;s tests]&lt;br /&gt;
* [http://mxr.mozilla.org/mozilla-central/find?string=test_.*%28html|svg%29%24&amp;amp;tree=mozilla-central&amp;amp;hint= Some of Mozilla&#039;s mochitests]&lt;br /&gt;
** [[Testsuite/Mozilla]]&lt;br /&gt;
* [http://mxr.mozilla.org/mozilla-central/find?string=reftest.list Some of Mozilla&#039;s reftests]&lt;br /&gt;
* [http://philip.html5.org/tests/canvas/suite/tests/ Philip&#039;s canvas tests]&lt;br /&gt;
* [http://hixie.ch/tests/adhoc/html/ Hixie&#039;s ad-hoc tests]&lt;br /&gt;
* [http://lachy.id.au/dev/markup/tests/html5/ Lachlan&#039;s tests]&lt;br /&gt;
* [http://hg.gsnedders.com/php-html-5-direct/file/tip/tests/numbersTest gsnedders&#039; number parsing tests]&lt;br /&gt;
* [http://simon.html5.org/test/html/ zcorpan&#039;s tests]&lt;br /&gt;
* [http://code.google.com/p/html5lib/source/browse/testdata html5lib tests]&lt;br /&gt;
* [http://hsivonen.iki.fi/test/moz/video-selection/ hsivonen&#039;s video tests]&lt;br /&gt;
* [http://www.w3.org/DOM/Test/ Document Object Model (DOM) Conformance Test Suites]&lt;br /&gt;
* [http://dev.w3.org/2006/webapi/WindowTestSuite/ Window test suite]&lt;/div&gt;</summary>
		<author><name>Maria</name></author>
	</entry>
</feed>