Re: git repos for tests?

Hi, Dirk.

This is great news.

Plan is to end up with all open web platform tests in the same repo (web-platform-tests). Hence the name. :)

Migrating to Git has proven more complex for certain groups (notably the CSS group). These are still considering their Mercurial repo as canonical for now. We hope this will change shortly.

LMK if there's anything I can help with.

Best,

--tobie 


On Wednesday, May 29, 2013 at 12:11 AM, Dirk Pranke wrote:

> Hi all,
> 
> I am currently working on getting chromium/blink (and webkit, hopefully) regularly running the w3c test suites. 
> 
> The general approach I am aiming for is to pull the test suites in directly from the repos with as few modifications as possible, and modify our testing harnesses to be able to automatically run them. At the moment it looks like we will need to do at least some minimal set of modifications to the tests (e.g., add -webkit- prefixes to CSS) and we have a script that can automatically make those modifications. 
> 
> My understanding (from talking to Tobie and others a while ago) is that we are moving all of the suites to repos on GitHub (i.e., github.com/w3c (http://github.com/w3c)). 
> 
> It looks like we have at least three repos cloned so far: csswg-test, web-performance, and web-platform-tests (which looks like a merge of html-testsuite and webapps).
> 
> Are there more repos I should be paying attention to (possibly not yet on github)?
> 
> Do we plan to eventually consolidate these three into a single repo, or do we want to keep the repo structure following the w3c's organizational structure in some form? 
> 
> For Blink, I am currently planning to create mirrors of these repos (largely for redundancy and network performance), and then create branches in these repos so I can check in the automatically-modified files. We will then pull the mirrors into our local builds and run the tests out of them. It's possible that it may make sense to merge the blink-specific branches upstream into the github repos at some point, if I can't stamp out the need for modifications altogether. 
> 
> I am still working through the details of the process, and will be providing feedback as I come to it :). That said, answers to the above questions and any other feedback you might have would be quite welcome. 
> 
> Cheers,
> 
> -- Dirk

Received on Tuesday, 28 May 2013 22:21:49 UTC