- From: James Graham <james@hoppipolla.co.uk>
- Date: Thu, 22 Aug 2013 17:31:24 +0100
- To: "public-test-infra@w3.org" <public-test-infra@w3.org>
A modified proposal: By default apply the following rules, in the order given: * Any file with a name starting with a . or equal to "override.manifest" is a helper file * Any file with -manual in the name before the extension is a manual test. * Any html, xhtml or svg file that links to testharness.js is a testharness test * Any html, xhtml or svg file that has a file with the same name but the suffix -ref before the extension is a reftest file and the corresponding -ref file is a helper file. * Any html, xhtml or svg file that contains a link rel=match or link rel=mismatch is a reftest file. * Any other file is a helper file. These rules can be overridden by providing an override.manifest file. Such a file can contain a list of filenames to exclude from the normal processing above and a list of urls for tests, similar to my previous proposal. So for example one might have [exclude] foo.html [testharness] foo.html?subset=1 foo.html?subset=2 I am still not sure how to deal with timeouts. One option would be to put the overall timeout in a meta value rather than in the javascript, since this will be easier to parse out. For tests where this doesn't work due to strong constraints on the html, one could use the override.manifest as above (and also specify the timeout in the js). I can't say I am thrilled with this idea though.
Received on Thursday, 22 August 2013 16:31:56 UTC