Auto-tools/Projects/W3C CSS Test Mirroring: Difference between revisions

Jump to navigation Jump to search
(Created page with "= Rationale = 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 in...")
 
Line 8: Line 8:
* 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 "accepted" tree into our other-licenses/w3c-css/tests (name TBD) directory.
* On some time sequence (once a day or something) we pull from the W3C "accepted" tree into our other-licenses/w3c-css/tests (name TBD) directory.
** When we pull the tests down, we will need to review the tests in the upstream directory and merge the
** When we pull the tests down, we need to generate the reftest manifests for the newly downloaded tests.
** Because these newly downloaded tests may exist in our upstream directory we need to ensure that the reftest manifest annotations those files had in the upstream directory are added to the generated manifest for the new file in the tests/ directory.
** Once the manifests are merged, the upstream test files (and their corresponding manifest entiries) should be deleted.
 
= Goal =
* Have an automated way to keep our W3C CSS reftests in sync with what is up in the "accepted" directory of the W3C and also help us have a mechanism to upload tests automatically.
 
= Non-Goal =
* Not to solve every corner case.  If the W3C ends up changing the name of the test between the "submitted" and the "accepted" step, we may lose the ability to track the test, and we'll have to deal with that manually.
 
= More Info =
* Talk to Elika about this - fantasai online
Confirmed users
3,816

edits

Navigation menu