- From: Tobie Langel <tobie.langel@gmail.com>
- Date: Thu, 24 Apr 2014 09:46:31 +0200
- To: Peter Linss <peter.linss@hp.com>
- Cc: Rebecca Hauck <rhauck@adobe.com>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>, Elika Etemad <fantasai@inkedblade.net>
On Apr 24, 2014, at 1:48, Peter Linss <peter.linss@hp.com> wrote: > I have no issue with this plan, but do note than many tests are linked to more than one spec and I expect that to get more common as specs evolve. So while we can adopt a simple convention, like put the test in the directory for the first linked spec, people will have to be aware that the files under a single directory are not the exhaustive list of the tests for that spec. Gathering and copying all the tests for a single spec into a single package is what the build scripts do. Have you considered symlinking for this? Or a similar, custom solution that the test runner would understand? --tobie
Received on Thursday, 24 April 2014 07:58:16 UTC