QA/Platform/DOM: Difference between revisions
Line 110: | Line 110: | ||
; [[Platform/Roadmap#DOM|Roadmap]] / [https://trello.com/b/HFf1xGCC/platform-status-board Trello] / [[QA/Platform/DOM/Feature_Testplan_Template|Template]] | ; [[Platform/Roadmap#DOM|Roadmap]] / [https://trello.com/b/HFf1xGCC/platform-status-board Trello] / [[QA/Platform/DOM/Feature_Testplan_Template|Template]] | ||
Firefox 40 (Nightly): | |||
* | * [https://trello.com/c/bqNlSEiO/444-screen-orientation-api Screen Orientation API] | ||
Firefox 39 (Aurora): | |||
* | * [https://trello.com/c/VxM3osuE/19-service-workers Service Workers] | ||
* | * [https://trello.com/c/OaQ85bvs/406-indexeddb-sqlite-performance-improvements IndexedDB & SQLite performance improvements] | ||
Firefox 38 (Beta): | |||
* [https://trello.com/c/16ShYTsh/13-picture-tag Picture Tag] | |||
* [https://trello.com/c/MtwzxobL/181-requestsync-api-2-2 RequestSync API] | |||
* [https://trello.com/c/qlwsobbB/407-broadcast-channel-api BroadcastChannel API] | |||
Firefox 37 (released March 31, 2015): | Firefox 37 (released March 31, 2015): | ||
* [https://trello.com/c/rdHssqZr/20-indexeddb-in-workers IndexedDB in Workers] | * [https://trello.com/c/rdHssqZr/20-indexeddb-in-workers IndexedDB in Workers] | ||
* [https://trello.com/c/7EJdOwmn/78-websockets-in-workers Web Sockets in Workers] | * [https://trello.com/c/7EJdOwmn/78-websockets-in-workers Web Sockets in Workers] |
Revision as of 19:35, 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
- 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:
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 |
|
4 | March 13, 2015 | DONE |
|
3 | February 27, 2015 | DONE |
|
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
Features
Firefox 40 (Nightly):
Firefox 39 (Aurora):
Firefox 38 (Beta):
Firefox 37 (released March 31, 2015):