Auto-tools/New Contributor/Quarter of Contribution/Web Driver Infrastructure
- Web Platform Tests – WebDriver Infrastructure
- Andreas Tolfsen (ato on IRC, GitHub)
The project is an attempt to provide tests that can be run in all browsers, giving browser vendors confidence that they are shipping software that is compatible with other browsers. This gives web authors assurance that they can rely on the web platform to deliver on the promise of working across browsers and devices, without needing extra layers of abstraction to cover the gaps left by specification editors and implementors.
wptrunner already uses WebDriver to drive the tests in a browser. It loads the test documents, listens for test results from testharness.js (the harness that wpt tests are written using), and then reports them back. By giving the in-browser content JS the ability to call out to the WebDriver session controlling its own browser session, the tests will be able to issue trusted OS events and emulate user interaction in a way that hasn’t previously been possible.
This project will allow the web platform to ensure cross-browser interoperability in privileged and permissions-guarded areas that content JS is not able to reach.
The project is outlined further in Github issue #2161.
To learn more about this project we recommend:
- Join IRC! It’s the best place to ask questions about the project and get help if you are stuck. #testing on irc.w3.org and #ateam on irc.mozilla.org are great channels to be in. Note that many people are most active in European timezones.
- Checkout web-platform-tests from GitHub. Make sure that you are able to start the server and load tests in your browser; see the README file for instructions on how to do this.
- If you’d like, try fixing one of the difficulty:easy bugs listed on the web-platform-tests issue tracker. These are generally not strictly related to this project, but they will help you understand the workings of web-platform-tests.
- Run the
manifestscript in your web-platform-tests checkout to generate a test manifest.
- Checkout wptrunner and try running a test against your local browser. See the README for more instructions, but something like:
wptrunner --binary=/path/to/firefox/binary --tests /path/to/web-platform-tests --metadata /path/to/web-platform-tests --ssl-type none --log-mach - dom/historical.html
- Alternatively, if you have a Firefox source tree and build, you can run web-platform-tests using mach:
mach web-platform-tests dom/historical.html.
- Read about manual test cases in WPT.
- Learn about WebDriver.
Things we are looking for in an ideal candidate:
- Willing to learn how to write WebDriver adaptors
- Eagerness to learn about network and socket programming, protocols, and serialisation
- Interest in test automation and UI/functional automation
- Willing to learn, ask questions, and try new things out