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 Chat (such as one of these permanent autoconfirmed members).
Testsuite: Difference between revisions
Jump to navigation
Jump to search
(Test metadata and automation) |
(Link to new format proposal) |
||
| Line 15: | Line 15: | ||
* 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.) | * 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 == | == Existing tests == | ||
Revision as of 19:05, 23 September 2009
Existing tests URI: http://dev.w3.org/html5/tests/
Requirements
- 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
- 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
- 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.