W3C home > Mailing lists > Public > public-html-testsuite@w3.org > February 2011

Re: Testing Requirements

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Thu, 17 Feb 2011 09:55:37 +0100
To: marcosc@opera.com
Cc: public-webapps@w3.org, "public-html-testsuite@w3.org" <public-html-testsuite@w3.org>, "fd@w3.org" <fd@w3.org>
Message-ID: <1297932937.14443.60.camel@altostratustier>
Hi Marcos,

Le mardi 15 février 2011 à 13:19 +0100, Marcos Caceres a écrit :
> Can we please get a full rundown of the systems available on test
> server. Can we also have all the details about getting access to the
> server, etc.

Here is what I know off the top of my head:
* the content on w3c-test.org reflects automatically the content of a
number of selected repositories of dvcs.w3.org ; the selection of
repositories can be extended by asking sysreq@w3.org and/or Francois

* w3c-test.org can be used to host any static files

* it can be used to host PHP scripts, but these scripts need to be
reviewed/approved by W3C Staff — this is done "transparently", i.e.
whenever a PHP script is committed, a number of us get a notification,
we review the changes and upon approval the PHP script is updated on the
server side

* the content of w3c-test.org is also available as www.w3c-test.org ,
www1.w3c-test.org  and www2.w3c-test.org to allow testing cross-domain

* it is also available under https as https://w3c-test.org/

(I see that Art documented most of this in
http://www.w3.org/2008/webapps/wiki/Testing_Requirements but thought
this ought to be confirmed on the list)

We would rather keep as many of the scripts in PHP to avoid making the
set up and maintenance of the server more complicated, but if/when we
need to run scripts in another language (e.g. Python), this can be
brought back on the table.

Received on Thursday, 17 February 2011 08:56:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:14:30 UTC