W3C home > Mailing lists > Public > public-test-infra@w3.org > January to March 2013

Re: Importing W3C's test suite into implementor's test suites.

From: James Graham <jgraham@opera.com>
Date: Thu, 21 Mar 2013 22:55:06 +0100 (CET)
To: Rebecca Hauck <rhauck@adobe.com>
cc: Dirk Pranke <dpranke@chromium.org>, Tobie Langel <tobie@w3.org>, Robin Berjon <robin@w3.org>, public-test-infra <public-test-infra@w3.org>, fantasai <fantasai.lists@inkedblade.net>, Kris Krueger <krisk@microsoft.com>
Message-ID: <alpine.DEB.2.02.1303212251260.7756@sirius>
On Thu, 21 Mar 2013, Rebecca Hauck wrote:

> FWIW, the reason I've started to address automating the import is 
> because I'm currently in a third scenario that hasn't really been 
> addressed directly here.  Where Scenario 1 is upstreaming existing tests 
> from implementors to the W3C and Scenario 2 is implementors importing 
> existing tests from the W3C, I'm currently in spot where I'm writing new 
> tests and want to submit them to both places at once.

[...]

> I'd be curious to know if any other implementors had a model for this 
> case. And sorry Tobie if I've just created another fork of this 
> discussion.

FWIW the model at Opera is that tests are written and reviewed internally 
and then submitted to W3C as a seperate step. This can involve some 
changes to the tests e.g. to change internal server names to W3C server 
names, although we have got better at either avoiding these problems or 
mitigating them. I'm not claiming that this is the best model, but I 
imagine there are a number of organisations that will not be submitting 
tests as soon as they are written, but waiting for a variety of reasons.
Received on Thursday, 21 March 2013 21:55:51 UTC

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