Confirmed users
3,376
edits
Auto-tools/Projects/web-platform-tests: Difference between revisions
Auto-tools/Projects/web-platform-tests (view source)
Revision as of 19:22, 10 March 2015
, 10 March 2015updated to be closer to newer project template format.
(Add contacts section) |
m (updated to be closer to newer project template format.) |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview / Problem = | ||
web-platform-tests is a testsuite designed for cross-browser testing of web features like CSS and DOM APIs. | web-platform-tests is a testsuite designed for cross-browser testing of web features like CSS and DOM APIs. | ||
Creating, and running, such a testsuite is a crucial part of improving the open web. Whenever a technology has multiple implementations it's very easy to introduce accidental discrepancies that cause poor interoperability. Historically this has been a problem on the web with different browsers all having their own quirks that developers have had to learn and work around. By contributing to the web-platform-tests testsuite we can build up a repository of test cases that can be run by all browser vendors through their development cycle so such issues are caught before they make it into released builds. | Creating, and running, such a testsuite is a crucial part of improving the open web. Whenever a technology has multiple implementations it's very easy to introduce accidental discrepancies that cause poor interoperability. Historically this has been a problem on the web with different browsers all having their own quirks that developers have had to learn and work around. By contributing to the web-platform-tests testsuite we can build up a repository of test cases that can be run by all browser vendors through their development cycle so such issues are caught before they make it into released builds. | ||
= Goals & Considerations = | |||
The aim of this project is to allow us to run the full set of web-platform-tests in Gecko and Servo, and create an easy workflow for contributing tests back upstream. | The aim of this project is to allow us to run the full set of web-platform-tests in Gecko and Servo, and create an easy workflow for contributing tests back upstream. | ||
= | = Non Goals = | ||
We are not aiming to own the entire set of tests or push our full set of tools to all other browser vendors. | |||
= Dependencies / Who will use this = | |||
The tests | The target here is Mozilla developers and release management. We run tests on every change to the browser and the feedback about passing/failing tests is important. Also updated/new tests need to run upstream so expect other vendors to run these tests. | ||
= Design & Approach = | |||
= Future | = Milestones / Future Work = | ||
* Improved support for upstreaming tests from gecko directly into the upstream repository. | * Improved support for upstreaming tests from gecko directly into the upstream repository. | ||
| Line 27: | Line 29: | ||
* More sophisticated reftest matching for cases where deterministic pixel equality isn't achievable. | * More sophisticated reftest matching for cases where deterministic pixel equality isn't achievable. | ||
= | = Implementation = | ||
The overall web-platform-tests project is hosted on [http://github.com/w3c/web-platform-tests github] and documented at [http://testthewebforward.org/docs testthewebforward.org]. This site contains notes on how to run and write tests. | |||
The tool we use for running the tests is [http://github.com/w3c/wptrunner wptrunner], which is documented on [https://readthedocs.org/projects/wptrunner/ readthedocs]. | |||
The tests use a custom web server, [http://github.com/w3c/wptserve wptserve], which also has documentation on [https://readthedocs.org/projects/wptrunner/ readthedocs]. | |||
Gecko-specific integration lives [http://dxr.mozilla.org/mozilla-central/source/testing/web-platform in-tree] and is documented in some [http://dxr.mozilla.org/mozilla-central/source/testing/web-platform/README.md README] files. | |||
= Getting Involved = | |||
Because a lot of the project is developed "upstream" on GitHub, not all of the bugs are in bugzilla.mozilla.org. | Because a lot of the project is developed "upstream" on GitHub, not all of the bugs are in bugzilla.mozilla.org. | ||
| Line 56: | Line 68: | ||
* [mailto:public-test-infra@w3.org public-test-infra@w3.org] ([https://lists.w3.org/Archives/Public/public-test-infra/ archives]) | * [mailto:public-test-infra@w3.org public-test-infra@w3.org] ([https://lists.w3.org/Archives/Public/public-test-infra/ archives]) | ||
== | == Team / irc == | ||
* jgraham | * [https://mozillians.org/en-US/u/jgraham/ jgraham] | ||
* Ms2ger | * [https://mozillians.org/en-US/u/ms2ger/ Ms2ger] | ||