Confirmed users
3,816
edits
Auto-tools/Projects/W3C CSS Test Mirroring: Difference between revisions
Auto-tools/Projects/W3C CSS Test Mirroring (view source)
Revision as of 23:41, 16 September 2011
, 16 September 2011→Proposed Process
| Line 11: | Line 11: | ||
** 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. | ** 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. | ** Once the manifests are merged, the upstream test files (and their corresponding manifest entiries) should be deleted. | ||
== Other considerations == | |||
We probably want to sync the W3C tests back into some kind of project branch. This way we can run the automated tests on them and let developers work on them to get them running and passing. The tests may need some specific Gecko reftest manifest annotation or something to get our tests to green. Once we get the tests to green, we can then merge them into mozilla-central. This last merge would be a manual step. | |||
= Goal = | = Goal = | ||