Re: Proposal to refactor the CSS test repo

On Apr 23, 2014, at 5:23 PM, L. David Baron <dbaron@dbaron.org> wrote:

> On Wednesday 2014-04-23 16:57 +0000, Rebecca Hauck wrote:
>> The proposed new structure:
>> 
>> tests/[spec-shortname, spec-shortname...]
>> test-plans/[spec-shortname, spec-shortname...]
>> tools
> 
> One issue with this is how to deal with tests where the master copy
> isn't in the CSSWG repository.
> 
> I've had a decent amount of success with getting developers who are
> writing Mozilla patches with tests for new Web platform features,
> where the tests ought to go in the CSSWG repository, to put those
> tests in a specific directory in the Mozilla repository, so that I
> can then occasionally import this directory to the CSSWG repository
> (in contributors/mozilla/submitted/mozilla-central-reftests).
> 
> This has worked reasonably well as an approach for getting tests
> written during Mozilla patch development into the CSSWG repository,
> and it has low enough overhead that tests actually end up in the
> CSSWG repository.  (This is despite substantial amounts of spec
> churn that require substantial changes to many of these tests.)
> 
> I'm not sure how to continue such an import procedure in this
> proposed new structure, in such a way that it would be low enough
> overhead to actually work.

I certainly don't want to introduce a change that's going to result in less tests getting into the repo (or staying in sync). 

Is the pain on your end that you'd need for the Mozilla tests to stay under a common directory or that the Mozilla repository would have to be refactored so that it could be mapped to the csswg repo?

Peter