- From: James Graham <james@hoppipolla.co.uk>
- Date: Tue, 23 Jul 2013 19:16:21 +0200
- To: <public-test-infra@w3.org>
>> Obviously no one is suggesting using file:// for testing since that >> has >> quite different semantics from HTTP. It already doesn't work to run >> even >> static tests over file:// since they depend on /resources/. > > It doesn't work when using a localhost server, either, which is > irritating, to be honest. Hmm? I typically check out web-platform-tests to ~/develop/web-platform-tests and testharness.js to ~/develop/testharness.js. Then ln -s ~/develop/web-platform-tests /var/www/tests ln -s ~/develop/testharness.js /var/www/resources and I can run all the tests from my local apache (i.e http://localhost/tests/) as I develop, with no post-processing required. Details differ depending on your platform of course, but this setup isn't as bad as you make it sound. Obviously the better long-term solution would be python testserver.py in the web-platform-tests checkout, which would route /resources/, and do a number of other things, for us. Of course this would require stopping anything already running on port 80 to set up the tests, but that doesn't seem like a huge burden compared to the advantages of having a single supported server optimized for running the tests.
Received on Tuesday, 23 July 2013 17:16:42 UTC