QA/Platform/DOM: Difference between revisions

From MozillaWiki
< QA‎ | Platform
Jump to navigation Jump to search
Line 45: Line 45:


= Triage =
= 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.
''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_DOM_team/Bug_Triage Triage]'' is the process of going through a list of bugs to identify and prioritize bugs for testing.
 
; Queries
* [http://bit.ly/1EeqRhC Top crashes] to make sure bugs are assigned and on track
* [http://bit.ly/1EeqRhC Top crashes] to make sure bugs are assigned and on track
* [http://mzl.la/1MHGYGb Regressions] to find bugs needing QA investigation
* [http://mzl.la/1MHGYGb Regressions] to find bugs needing QA investigation
Line 51: Line 53:
* [http://mzl.la/1MvHsx1 Intermittent failures] to find bugs needing QA investigation
* [http://mzl.la/1MvHsx1 Intermittent failures] to find bugs needing QA investigation
* [http://mzl.la/1MvEaK1 Resolved bugs] to find bugs needing better test coverage or manual verification
* [http://mzl.la/1MvEaK1 Resolved bugs] to find bugs needing better test coverage or manual verification
[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Helping_the_DOM_team/Bug_Triage Read our guide] to learn more about triage.


; Backlog
; Backlog

Revision as of 20:30, 4 May 2015

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

Triage

Triage is the process of going through a list of bugs to identify and prioritize bugs for testing.

Queries
Backlog

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
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Platform/DOM&oldid=1072070"