QA/Platform/DOM/Ramp Up

Ramp Up

People

• Lead: Andrew Overholt
• Mentors: Ehsan Akhgari, Anne van Kesteren, Josh Matthews, Boris Zbarsky

2015 Roadmap

• Web Platform Tests
  • Automated cross-browser testing of features that involve UI (e.g. permission UI)
• Web Components
• Service Workers
• Making bugs actionable
  • Communicating with the bug reporter to ask them about the specifics of their report
  • Attempting to reproduce the bugs, perhaps by writing test cases
  • Gaining an understanding of who works on what in DOM, to be able to get the right eyes on bugs
  • Providing regression ranges and ideally identifying the commit that regressed something
  • Using various debugging tools (such as the built-in devtools, gdb, address sanitizer, rr, etc.) to gain more information on bugs
• Exploratory testing new DOM features before we ship them - in particular breaking things by doing stuff the developer didn't think of - if it's automated (e.g. fuzzers) so much the better

Documentation

• MDN
• How to build Nightly (Developer build of Firefox)
  • If you don't have mercurial installed, follow instructions to do so here: https://developer.mozilla.org/en-US/docs/Installing_Mercurial
  • To get, build and run mozilla-central (Nightly version of Firefox), follow the instruction here: https://developer.mozilla.org/en-US/docs/Simple_Firefox_build
• How to setup git.
  • get and install git from: http://www.git-scm.com/downloads
    • (optional) You may also want to use a git GUI. Here's a popular version: GitHub from http://www.git-scm.com/downloads/guis.
• Get the web-platform-tests and run them from the browser
  • With git is installed, in a terminal, run "git clone https://github.com/w3c/web-platform-tests.git"
  • Complete instructions for running the tests from the browser are here: https://github.com/w3c/web-platform-tests/blob/master/README.md
• Run the web-platform-tests of the Nightly build.
  • Instructions are here: https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/README.md
  • For example, to run the dom javascript tests:
    • 1. <hg pull and update your mozilla-central - steps here depend on how you set up your mozilla-central directory>
    • 2. cd <mozilla-central>
    • 3. ./mach build (./mach clobber may be required)
    • 4. ./mach web-platform-tests --test-type=testharness --include=dom
• How to bisect
  • If you are working on a bug that needs a regression range and there are reliable reproducible steps, try http://mozilla.github.io/mozregression/. If you can narrow it down to a one day regression window, add that information to the bug. Narrowing the window further down to a particular check-in may often be asked for, but that is another process in itself.
• wiki

Mailing Lists

• mozilla.dev.platform
• mozilla.dev.webapi