QA/Platform/DOM

From MozillaWiki
Jump to navigation Jump to search

About the Team

People

  • Manager: Andrew Overholt (overholt)
  • Engineers: Ehsan Akhgari (ehsan), Anne van Kesteren (annevk), Josh Matthews (jdm), Boris Zbarsky (bz)
  • QA: Anthony Hughes (ashughes)

How to Contact Us

Meetings

Meetings are pending approval of bug triage processes. Once this is approved we will go ahead and set up a recurring meeting.

Strategy

This page documents the QA strategy for testing Mozilla's DOM implementation. Our primary objective is the continuous improvement of DOM quality through two-week sprints of open, transparent, and data-driven qualification processes.

Documentation

Guides:

Reference:

Current Initiatives

Develop documentation to enable greater transparency of DOM testing standards and practices.

  • [DONE] Document how bugs are logged and triaged, including different types of bugs and how they're prioritized
  • [DONE] Develop a feature testplan template and begin documenting in-flight features
  • Develop a map of the dependencies DOM has on other components

Develop a suite of metrics to measure the overall health of Gecko's DOM implementation and the QA impact.

  • [DONE] Create an initial set of rudimentary metrics based on Bugzilla data to measure bug workflow effectiveness (wiki)
  • Review the metrics and automate them if they are deemed informative, investigate new metrics if not

Improve flow and resolution of bugs

  • Set up processes for bug triage including documentation and meetings
  • Create a backlog of bug-work for QA and begin working through that backlog
  • Improve coverage of the web-platform-tests

Sprints

Sprint Deadline Status Deliverables
5 March 20, 2015 IN PROGRESS
  • [DONE] make sure all DOM crashes >1% are reported
  • [ON TRACK] set up triage meeting once MDN documentation is reviewed
  • [ON TRACK] create patch for web-platform-tests#1506
  • [ON TRACK] review Betabreakers Firefox 38 testing (testplan)
  • Late Additions:
4 March 13, 2015 DONE
  • [CARRY OVER] set up a recurring triage meeting that is open to the public
    • delayed pending feedback on MDN documentation
  • [DONE] review and revise existing bug workflow documentation (migrate to MDN)
  • [DONE] review and revise the strategy and make sure all ramp up items are accounted for
  • [CARRY OVER] create an initial patch for web-platform-tests#1506
    • delayed due to Betabreakers Firefox 38 testing being moved up to Aurora
3 February 27, 2015 DONE
  • [DONE] Anthony to mock up something with unconfirmed bugs
  • [DONE] Get DOM team (Andrew and whoever else) to review benchmarks and metrics from bugzilla
  • [DROPPED] If benchmarks pass muster Anthony to look at automating them/metrics.js etc
    • delayed to Q2 due to competing priorities
  • [CARRY OVER] Tracy to set up bug triage
    • handed off to Anthony due to re-org
  • [CARRY OVER] Tracy to document the bug workflow w.r.t. verification (ie. when do we verify a bug)
    • handed off to Anthony due to re-org
  • [DONE] Revise the big to-do list above into a strategy of what will be done and when
  • [DROPPED] Look into what "developer preview" actually means w.r.t. service workers.
    • not sure what this was in regards to
  • [CARRY OVER] Review ramp up to make sure everything is completed or tracked
    • handed off to Anthony due to re-org

Triage

The team will meet once per week to go through the following reports in an effort to make sure bugs are moving forward toward resolution.

Read our guide to learn more about triage.

Backlog

Features

Roadmap / Trello / Template

Nightly

Aurora

  • [ON TRACK] Service Workers: Bugzilla, Trello, Wiki (unassigned)
  • [ON TRACK] IndexedDB/SQLite Performance: Bugzilla, Trello, Wiki (unassigned)

Beta

Released

Firefox 37 (March 31, 2015)

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Platform/DOM&oldid=1064947"