- From: James Graham <james@hoppipolla.co.uk>
- Date: Thu, 26 Feb 2015 18:05:21 +0000
- To: Philippe Le Hegaret <plh@w3.org>, "public-test-infra@w3.org" <public-test-infra@w3.org>
On 26/02/15 18:02, Philippe Le Hegaret wrote: > > On 02/26/2015 05:13 AM, James Graham wrote: >> So there are some cases in which it is useful to have multiple tests per >> file, distinguished by a query string or fragment. In fact some tests in >> the repo (e.g. the html5lib parser tests) already support variations >> specified in this way, but we don't include those variations in our >> manifest. >> >> Assuming we want to support this somehow, what's people's preferred >> mechanism? <meta> elements like: >> >> <meta name=test content=""> >> <meta name=test content="?variant=1"> >> >> An override.manifest file like: >> >> test.html >> test.html?variant=1 >> >> Something else? >> > > Would we want to let the test generate those variants automatically? ie > would there be a use case where those variants are constructed on the fly? No. This is for statically defined variants. If you want to construct different possibilities on the fly you can do that with js already (although there are good reasons to avoid it).
Received on Thursday, 26 February 2015 18:05:46 UTC