- From: Tobie Langel <tobie@w3.org>
- Date: Fri, 16 Aug 2013 21:59:38 +0200
- To: Dirk Pranke <dpranke@chromium.org>
- Cc: James Graham <james@hoppipolla.co.uk>, public-test-infra <public-test-infra@w3.org>
On Friday, August 16, 2013 at 9:33 PM, Dirk Pranke wrote: > Apart from the ones described above, it's not obvious to me that a naming convention like "all html files that aren't tests belong in a directory named ./resources, and no tests should be in that subdirectory" has particularly significant drawbacks? The only one that leaps out at me is if you want to use one test as a reference for another test, but the rule I just wrote doesn't actually preclude that. Similarly, being able to easily identify from name or location which tests were jstests, or reftest, or especially manual/pixel tests, would be tremendously useful. Couldn't agree more. --tobie
Received on Friday, 16 August 2013 19:59:47 UTC