715
edits
Auto-tools/New Contributor/Quarter of Contribution/Web Driver Infrastructure: Difference between revisions
Auto-tools/New Contributor/Quarter of Contribution/Web Driver Infrastructure (view source)
Revision as of 07:05, 31 October 2015
, 31 October 2015restructure and import learning section from wptrunner
(some improvement) |
(restructure and import learning section from wptrunner) |
||
| Line 3: | Line 3: | ||
;Mentor | ;Mentor | ||
:Andreas Tolfsen (''ato'' on IRC, [https://github.com/andreastt/ GitHub]) | :Andreas Tolfsen (''ato'' on IRC, [https://github.com/andreastt/ GitHub]) | ||
==Background== | |||
The [https://github.com/w3c/web-platform-tests Web Platform Tests] are part of the [http://www.w3.org/ W3C]-coordinated initiative ''[http://testthewebforward.org/ Test the Web Forward]'' to build a cross-browser testsuite for open web platform technologies. | The [https://github.com/w3c/web-platform-tests Web Platform Tests] are part of the [http://www.w3.org/ W3C]-coordinated initiative ''[http://testthewebforward.org/ Test the Web Forward]'' to build a cross-browser testsuite for open web platform technologies. | ||
| Line 8: | Line 10: | ||
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. | 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. | ||
==Project Outline== | |||
A yet unsolved problem is that not all test cases can be automated using | |||
content JavaScript; we’re lacking a way to control- and test features that require user input. The goal of this contribution is to allow [https://github.com/w3c/wptrunner wptrunner], the Web Platform Tests runner harness, to automatically run tests that would ordinarily require user interaction, through the [https://w3c.github.io/webdriver/webdriver-spec.html WebDriver protocol]. | content JavaScript; we’re lacking a way to control- and test features that require user input. The goal of this contribution is to allow [https://github.com/w3c/wptrunner wptrunner], the Web Platform Tests runner harness, to automatically run tests that would ordinarily require user interaction, through the [https://w3c.github.io/webdriver/webdriver-spec.html WebDriver protocol]. | ||
In more detail, the goal of this project is to implement a "meta-circular" WebDriver client. This will have an API implemented in JavaScript that runs into the browser. The API will use an HTTP or WebSockets backend to call a WebDriver client implemented in Python in the [https://github.com/w3c/wptserve wptserve] server. This Python code will in turn call back into the browser using the WebDriver API, enabling emulation of human-like interactions to happen from tests written purely in cross-browser JavaScript. | In more detail, the goal of this project is to implement a "meta-circular" WebDriver client. This will have an API implemented in JavaScript that runs into the browser. The API will use an HTTP or WebSockets backend to call a WebDriver client implemented in Python in the [https://github.com/w3c/wptserve wptserve] server. This Python code will in turn call back into the browser using the WebDriver API, enabling emulation of human-like interactions to happen from tests written purely in cross-browser JavaScript. | ||
The project is outlined further in [https://github.com/w3c/web-platform-tests/issues/2161 Github issue #2161]. | |||
==Learn more== | |||
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 [https://github.com/w3c/web-platform-tests 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 [https://github.com/w3c/web-platform-tests/labels/difficulty%3Aeasy 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 <code>manifest</code> script in your web-platform-tests checkout to generate a test manifest. | |||
* Checkout [https://github.com/w3c/wptrunner wptrunner] and try running a test against your local browser. See the README for more instructions, but something like: | |||
<code>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</code> | |||
* Alternatively, if you have a Firefox source tree and build, you can run web-platform-tests using mach: <code>mach web-platform-tests dom/historical.html</code> | |||
* Read about [https://github.com/w3c/web-platform-tests/blob/master/docs/manual-test.md manual test cases] in WPT. | |||
* Learn about [https://w3c.github.io/webdriver/webdriver-spec.html WebDriver] | |||
==Things we are looking for in an ideal candidate== | ==Things we are looking for in an ideal candidate== | ||
* Ability to write code and design good APIs in JavaScript and Python | * Ability to write code and design good APIs in both JavaScript and Python | ||
* Willing to learn how to write WebDriver adaptors | * Willing to learn how to write WebDriver adaptors | ||
* Creative ideas on how to proxy data between JavaScript and Python | * Creative ideas on how to proxy data between JavaScript and Python | ||
* Interest in test automation and UI automation | * 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 | * Willing to learn, ask questions, and try new things out | ||