Changes

Jump to: navigation, search

Auto-tools/Projects/web-platform-tests

569 bytes added, 19:22, 10 March 2015
m
updated to be closer to newer project template format.
= Overview / Problem =
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.
 
= 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.
= Source and Documentation Non Goals =
The overall web-platform-We are not aiming to own the entire set of 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 or push our full set of tools to run and write testsall other browser vendors.
The tool we = Dependencies / Who will use for running the tests is [http://github.com/w3c/wptrunner wptrunner], which is documented on [https://readthedocs.org/projects/wptrunner/ readthedocs].this =
The target here is Mozilla developers and release management. We run tests use a custom web server, [http://github.com/w3c/wptserve wptserve], which also has documentation on [https:every change to the browser and the feedback about passing//readthedocsfailing tests is important.org Also updated/projects/wptrunner/ readthedocs]new tests need to run upstream so expect other vendors to run these tests.
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.= Design & Approach =
= Milestones / Future Project Goals Work =
* Improved support for upstreaming tests from gecko directly into the upstream repository.
* More sophisticated reftest matching for cases where deterministic pixel equality isn't achievable.
= Bugs 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.
* [mailto:public-test-infra@w3.org public-test-infra@w3.org] ([https://lists.w3.org/Archives/Public/public-test-infra/ archives])
== Individuals Team / irc ==
* [https://mozillians.org/en-US/u/jgraham/ jgraham]* [https://mozillians.org/en-US/u/ms2ger/ Ms2ger]
Confirm
3,376
edits

Navigation menu