Confirmed users
104
edits
Auto-tools/Projects/W3C CSS Test Mirroring: Difference between revisions
Auto-tools/Projects/W3C CSS Test Mirroring (view source)
Revision as of 00:02, 17 September 2011
, 17 September 2011tweak some names and details, add links
(tweak some names and details, add links) |
|||
| Line 2: | Line 2: | ||
The W3C CSS Test working group has a bunch of tests in their hg repo on the W3C site. We need an automated way to pull the tests back from the W3C site into our infrastructure so that these tests can be run in addition to the rest of our automated test suites. | The W3C CSS Test working group has a bunch of tests in their hg repo on the W3C site. We need an automated way to pull the tests back from the W3C site into our infrastructure so that these tests can be run in addition to the rest of our automated test suites. | ||
We also need a way to automatically annotate new tests for inclusion into the upstream W3C repo. As a point of process, when a test is submitted to the W3C, it goes into a "submitted" tree, and then once it is accepted it is in an " | We also need a way to automatically annotate new tests for inclusion into the upstream W3C repo. As a point of process, when a test is submitted to the W3C, it goes into a "submitted" tree, and then once it is accepted it is in an "approved" tree. This is important to remember for the process outlined below. | ||
= Proposed Process = | = Proposed Process = | ||
* Developer writes test | * Developer writes test to be synced to W3C - these have a separate license, so they land in the other-licenses/ directory (fantasai will determine the proper directory for this), for now, let's call it other-licenses/w3c-css/submitted | ||
* An hg hook watches for checkins to this directory and causes the new test to be pushed into the W3C "submitted" tree. | * An hg hook watches for checkins to this directory and causes the new test to be pushed into the W3C "submitted" tree. | ||
* On some time sequence (once a day or something) we pull from the W3C " | * On some time sequence (once a day or something) we pull from the W3C "approved" tree into our other-licenses/w3c-css/received (name TBD) directory. | ||
** When we pull the tests down, we need to generate the reftest manifests for the newly downloaded tests. | ** When we pull the tests down, we need to generate the reftest manifests for the newly downloaded tests. (Note: W3C has build scripts that can generate reftest manifests.) | ||
** Because these newly downloaded tests may exist in our | ** Because these newly downloaded tests may exist in our submitted directory we need to ensure that the reftest manifest annotations those files had in the submitted directory are added to the generated manifest for the new file in the received/ directory. | ||
** Once the manifests are merged, the | ** Once the manifests are merged, the submitted test files (and their corresponding manifest entries) should be deleted. | ||
== Other considerations == | == Other considerations == | ||
| Line 16: | Line 16: | ||
= Goal = | = Goal = | ||
* Have | * Incorporate W3C-hosted CSS reftests into our automated testing framework | ||
* Have a place and process for devs to land tests that should be submitted to W3C | |||
* Keep our copy and W3C's copy of the tests in sync | |||
= Non-Goal = | = Non-Goal = | ||
| Line 22: | Line 24: | ||
= More Info = | = More Info = | ||
* | * CSSWG test server - http://test.csswg.org/ | ||
* CSSWG test wiki - http://wiki.csswg.org/test | |||
* Questions? Ask [http://fantasai.inkedblade.net/contact fantasai] | |||