QA/Platform/DOM

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

• Use the #content channel on irc.mozilla.org to chat with us in real-time
• Use the dev-platform mailing list to participate in on-going discussions

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:

• DOM Developer Guide
• How to install Mercurial
• How to build Firefox
• How to run the web platform tests
• Helping DOM QA [draft]

Reference:

• DOM APIs
• WebAPI wiki page
• Feature Roadmap
• Feature Testplan Template

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

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.

• Top crashes to make sure bugs are assigned and on track
• Regressions to find bugs needing QA investigation
• Unconfirmed bugs to find bugs needing QA investigation
• Intermittent failures to find bugs needing QA investigation
• Resolved bugs to find bugs needing better test coverage or manual verification

Read our guide to learn more about triage.

Backlog

• Requests for investigation
• Requests for verification
• Requests for automation

Features

Roadmap / Trello / Template

Feature	Target Milestone	Assignee	Tracking Bug	Development	Testing
Screen Orientation API	Firefox 40 (August 11, 2015)	William Chen [:wchen]	bug 1043102	IN PROGRESS
Service Workers	Firefox 39 (June 30, 2015)	Nikhil Marathe [:nsm]	bug 903441	IN PROGRESS
IndexedDB/SQLite Performance	Firefox 39 (June 30, 2015)	Ben Turner [:bent]	several	DONE	PENDING FEEDBACK
Picture Tag	Firefox 38 (May 12, 2015)	John Schoenick [:johns]	bug 870022	DONE	PENDING FEEDBACK
BroadcastChannel API	Firefox 38 (May 12, 2015)	Andrea Marchesini [:baku]	bug 966439	DONE	DONE
IndexedDB in Workers	Firefox 37 (March 31, 2015)	Ben Turner [:bent]	bug 701634	DONE	DONE
Web Sockets in Workers	Firefox 37 (March 31, 2015)	Andrea Marchesini [:baku]	bug 504553	DONE	DONE