https://wiki.mozilla.org/api.php?action=feedcontributions&user=Ctalbert&feedformat=atomMozillaWiki - User contributions [en]2024-03-28T21:06:29ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1059767QA/Goals/2015q12015-03-04T18:59:40Z<p>Ctalbert: /* DOM */</p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Deliberate<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Impact<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Mozfactor<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Overall Quality<br />
| style="font-weight: bold; background: #DDD; width: 48%" | Rationale<br />
|-<br />
| Firefox 35<br />
| Jan 12 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Firefox 36<br />
| Feb 23 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Spring Release Planning<br />
| Ongoing<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| New Embedded Team Sprints<br />
| ongoing<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Marionette Training and Test Conversion<br />
| Feb 1 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
== Prioritized Tasks ==<br />
* [ON TRACK] [mbrandt/bsilverberg] - Identify and deliver on the highest priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)<br />
** Identified in https://www.pivotaltracker.com/n/projects/280483<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "[https://github.com/mozilla/firefox-ui-tests Green-light]" test framework in preparation for E10s}}<br />
** Training: an incomplete (missing the 1st part) video was posted to Air Mozilla: https://air.mozilla.org/mozmill-to-marionette-conversion-bootcamp-training/<br />
*** It's being down-converted and will be reposted [https://bugzilla.mozilla.org/show_bug.cgi?id=1136408 bug 1136408]<br />
** Remaining conversion work in dependencies from this tracking bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1129843 bug 1129843]<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{done|<small>[lizzard, juanb]</small> - Establish baselines for automated-test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}}<br />
** We did this for addons, automated tests, and crash stats. Memory footprint did not seem like a reliable metric to track at this time given the amount of work required and the amount of variability in the data. <br />
* {{risk|<small>[lizzard, juanb]</small> - Improve the automated-test coverage for E10s-enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
** This is {{bug|1122901}}. It is now in the hands of the automation team and the releng team and while we are pushing on it, it's not entirely in our control anymore.<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve add-on compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{done|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{risk|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing Web-platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast-running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
* {{ok|<small>[aaronmt, kbrosnan]</small> - Slim down the per-release smoketest by at least 25%}}<br />
* {{ok|<small>[kbrosnan]</small> - Investigate using Marionette/Firefox Green-light on Fennec, create a plan and prioritized set of targets for the Marionette team}}<br />
* {{ok|<small>[aaronmt]</small> - Fix or discontinue appthwak automation}}<br />
<br />
== Web QA ==<br />
* {{done|<small>[rbillings]</small> - Promulgate the usage of One and Done beyond QA: meet with at least one other team [ex: CBT, Security] to educate them on what O&D does and how they might use it and detail out the changes that would be required to update the scope of the site beyond QA.}}<br />
* {{done|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{done|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
** this is to support, and have a dependency on, Kairo's goal under "General Quality," above<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 - Make Web QA's Jenkins public}}<br />
** Done! Just awaiting on docs and a blog post to officially mark this: https://webqa-ci.mozilla.com/<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>Identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)]}} <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require add-on signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on YouTube by supporting the media team in shipping MSE on YouTube for Windows Vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1059766QA/Goals/2015q12015-03-04T18:59:18Z<p>Ctalbert: /* DOM */</p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Deliberate<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Impact<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Mozfactor<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Overall Quality<br />
| style="font-weight: bold; background: #DDD; width: 48%" | Rationale<br />
|-<br />
| Firefox 35<br />
| Jan 12 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Firefox 36<br />
| Feb 23 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Spring Release Planning<br />
| Ongoing<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| New Embedded Team Sprints<br />
| ongoing<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Marionette Training and Test Conversion<br />
| Feb 1 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
== Prioritized Tasks ==<br />
* [ON TRACK] [mbrandt/bsilverberg] - Identify and deliver on the highest priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)<br />
** Identified in https://www.pivotaltracker.com/n/projects/280483<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "[https://github.com/mozilla/firefox-ui-tests Green-light]" test framework in preparation for E10s}}<br />
** Training: an incomplete (missing the 1st part) video was posted to Air Mozilla: https://air.mozilla.org/mozmill-to-marionette-conversion-bootcamp-training/<br />
*** It's being down-converted and will be reposted [https://bugzilla.mozilla.org/show_bug.cgi?id=1136408 bug 1136408]<br />
** Remaining conversion work in dependencies from this tracking bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1129843 bug 1129843]<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{done|<small>[lizzard, juanb]</small> - Establish baselines for automated-test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}}<br />
** We did this for addons, automated tests, and crash stats. Memory footprint did not seem like a reliable metric to track at this time given the amount of work required and the amount of variability in the data. <br />
* {{risk|<small>[lizzard, juanb]</small> - Improve the automated-test coverage for E10s-enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
** This is {{bug|1122901}}. It is now in the hands of the automation team and the releng team and while we are pushing on it, it's not entirely in our control anymore.<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve add-on compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{done|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{ok|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing Web-platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast-running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
* {{ok|<small>[aaronmt, kbrosnan]</small> - Slim down the per-release smoketest by at least 25%}}<br />
* {{ok|<small>[kbrosnan]</small> - Investigate using Marionette/Firefox Green-light on Fennec, create a plan and prioritized set of targets for the Marionette team}}<br />
* {{ok|<small>[aaronmt]</small> - Fix or discontinue appthwak automation}}<br />
<br />
== Web QA ==<br />
* {{done|<small>[rbillings]</small> - Promulgate the usage of One and Done beyond QA: meet with at least one other team [ex: CBT, Security] to educate them on what O&D does and how they might use it and detail out the changes that would be required to update the scope of the site beyond QA.}}<br />
* {{done|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{done|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
** this is to support, and have a dependency on, Kairo's goal under "General Quality," above<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 - Make Web QA's Jenkins public}}<br />
** Done! Just awaiting on docs and a blog post to officially mark this: https://webqa-ci.mozilla.com/<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>Identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)]}} <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require add-on signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on YouTube by supporting the media team in shipping MSE on YouTube for Windows Vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1059765QA/Goals/2015q12015-03-04T18:58:58Z<p>Ctalbert: /* E10s */</p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Deliberate<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Impact<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Mozfactor<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Overall Quality<br />
| style="font-weight: bold; background: #DDD; width: 48%" | Rationale<br />
|-<br />
| Firefox 35<br />
| Jan 12 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Firefox 36<br />
| Feb 23 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Spring Release Planning<br />
| Ongoing<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| New Embedded Team Sprints<br />
| ongoing<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Marionette Training and Test Conversion<br />
| Feb 1 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
== Prioritized Tasks ==<br />
* [ON TRACK] [mbrandt/bsilverberg] - Identify and deliver on the highest priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)<br />
** Identified in https://www.pivotaltracker.com/n/projects/280483<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "[https://github.com/mozilla/firefox-ui-tests Green-light]" test framework in preparation for E10s}}<br />
** Training: an incomplete (missing the 1st part) video was posted to Air Mozilla: https://air.mozilla.org/mozmill-to-marionette-conversion-bootcamp-training/<br />
*** It's being down-converted and will be reposted [https://bugzilla.mozilla.org/show_bug.cgi?id=1136408 bug 1136408]<br />
** Remaining conversion work in dependencies from this tracking bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1129843 bug 1129843]<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{done|<small>[lizzard, juanb]</small> - Establish baselines for automated-test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}}<br />
** We did this for addons, automated tests, and crash stats. Memory footprint did not seem like a reliable metric to track at this time given the amount of work required and the amount of variability in the data. <br />
* {{risk|<small>[lizzard, juanb]</small> - Improve the automated-test coverage for E10s-enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
** This is {{bug|1122901}}. It is now in the hands of the automation team and the releng team and while we are pushing on it, it's not entirely in our control anymore.<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve add-on compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{ok|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{ok|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing Web-platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast-running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
* {{ok|<small>[aaronmt, kbrosnan]</small> - Slim down the per-release smoketest by at least 25%}}<br />
* {{ok|<small>[kbrosnan]</small> - Investigate using Marionette/Firefox Green-light on Fennec, create a plan and prioritized set of targets for the Marionette team}}<br />
* {{ok|<small>[aaronmt]</small> - Fix or discontinue appthwak automation}}<br />
<br />
== Web QA ==<br />
* {{done|<small>[rbillings]</small> - Promulgate the usage of One and Done beyond QA: meet with at least one other team [ex: CBT, Security] to educate them on what O&D does and how they might use it and detail out the changes that would be required to update the scope of the site beyond QA.}}<br />
* {{done|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{done|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
** this is to support, and have a dependency on, Kairo's goal under "General Quality," above<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 - Make Web QA's Jenkins public}}<br />
** Done! Just awaiting on docs and a blog post to officially mark this: https://webqa-ci.mozilla.com/<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>Identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)]}} <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require add-on signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on YouTube by supporting the media team in shipping MSE on YouTube for Windows Vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2015-03-04&diff=1058774QA/Team Meeting/QA Team Meeting-2015-03-042015-02-27T21:38:20Z<p>Ctalbert: /* Discussion & Updates for Team */</p>
<hr />
<div>= Mozilla QA Meeting March 4, 2015 =<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
<br />
== Actions From Last Week ==<br />
<br />
== Deadlines and Schedules ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
=== Other Notable Dates/Events (Read Only) ===<br />
*<br />
<br />
== Discussion & Updates for Team ==<br />
* <small>''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''</small><br />
* This meeting, going forward<br />
* Fx OS V3 idea announcement last week<br />
* QA Tea Time reminder - https://etherpad.mozilla.org/QA-tea-time<br />
* [ashughes] Organizing Test Days going forward<br />
<br />
== Lightning Talk ==<br />
* <small>''[[QA/Team_Meeting/Lightning Talk List|Lightning talk list]]''</small><br />
<br />
== Contributors ==<br />
=== New Contributor Spotlight ===<br />
These are new contributors, if you see them around, say hello<br />
*<br />
<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO (Read Only) ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting&diff=1058380QA/Team Meeting2015-02-25T23:32:29Z<p>Ctalbert: </p>
<hr />
<div>Our every 2 week meeting is open to the public. You're welcome to join.<br />
<br />
== Meeting Details ==<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Angel conference room.<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23qa irc://irc.mozilla.org:6697/#qa]<br />
<br />
* Please see below for next meeting date and previous archived meetings<br />
* [[QA/Team_Meeting/QA_Team_Template|Team Meeting Template]]<br />
* [[QA/StaffMeetings/videos| Videos of meetings]]<br />
<createbox><br />
align=left<br />
type=create<br />
preload=QA/Team_Meeting/QA_Team_Template<br />
default={{#time: Y-m-d | wednesday}}<br />
prefix=QA/Team_Meeting/QA_Team_Meeting-<br />
</createbox><br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2015 <br />
|-<br />
|<br />
* March 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-03-04|All Quality Meeting Mar 4]]<br />
* February 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-02-18|All Quality Meeting Feb 18]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-02-04|All Quality Meeting Feb 4]]<br />
* January 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-21|All Quality Meeting Jan 21]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-14|All Quality Meeting Jan 14]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-07|All Quality Meeting Jan 7]]<br />
|}<br />
<br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2014 <br />
|-<br />
|<br />
* December 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-17|QA Team Meeting Dec 17]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-10|QA Team Meeting Dec 10]]<br />
* November 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-26|QA Team Meeting Nov 26]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-19|QA Team Meeting Nov 19]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-12|QA Team Meeting Nov 12]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-05|QA Team Meeting Nov 5]]<br />
* October 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-29|QA Team Meeting Oct 29]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-22|QA Team Meeting Oct 22]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-15|QA Team Meeting Oct 15]]<br />
** QA Team Meeting Oct 08 - CANCELED<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-01|QA Team Meeting Oct 01]]<br />
*September 2014<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-24 | QA Team Meeting Sept 24]]<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-17 | QA Team Meeting Sept 17]]<br />
**[[QA/Team_Meeting/QA-Team-2014-09-10 | QA Team Meeting Sept 10]]<br />
**[[QA/Team_Meeting/QA-Team-09-03-2014 | QA Team Meeting Sept 3]]<br />
*August 2014<br />
**[[QA/StaffMeetings/QA-Staff-08-27-2014|QA-Staff-08-27-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-20-2014|QA-Staff-08-20-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-13-2014|QA-Staff-08-13-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-06-2014|QA-Staff-08-06-2014]]<br />
*July 2014<br />
** Meeting on July 30 was canceled due to QA Work Week<br />
**[[QA/StaffMeetings/QA-Staff-07-23-2014|QA-Staff-07-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-16-2014|QA-Staff-07-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-09-2014|QA-Staff-07-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-02-2014|QA-Staff-07-02-2014]]<br />
*June 2014<br />
**[[QA/StaffMeetings/QA-Staff-06-25-2014|QA-Staff-06-25-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-18-2014|QA-Staff-06-18-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-11-2014|QA-Staff-06-11-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-04-2014|QA-Staff-06-04-2014]]<br />
*May 2014<br />
**[[QA/StaffMeetings/QA-Staff-05-28-2014|QA-Staff-05-28-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-21-2014|QA-Staff-05-21-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-14-2014|QA-Staff-05-14-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-07-2014|QA-Staff-05-07-2014]]<br />
*April 2014<br />
**[[QA/StaffMeetings/QA-Staff-04-30-2014|QA-Staff-04-30-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-23-2014|QA-Staff-04-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-16-2014|QA-Staff-04-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-09-2014|QA-Staff-04-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-02-2014|QA-Staff-04-02-2014]]<br />
*March 2014<br />
**[[QA/StaffMeetings/QA-Staff-03-26-2014|QA-Staff-03-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-19-2014|QA-Staff-03-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-12-2014|QA-Staff-03-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-05-2014|QA-Staff-03-05-2014]]<br />
*February 2014<br />
**[[QA/StaffMeetings/QA-Staff-02-26-2014|QA-Staff-02-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-19-2014|QA-Staff-02-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-12-2014|QA-Staff-02-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-05-2014|QA-Staff-02-05-2014]]<br />
*January 2014<br />
**[[QA/StaffMeetings/QA-Staff-01-29-2014|QA-Staff-01-29-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-22-2014|QA-Staff-01-22-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-15-2014|QA-Staff-01-15-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-08-2014|QA-Staff-01-08-2014]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2013<br />
|-<br />
|<br />
*December<br />
**[[QA/StaffMeetings/QA-Staff-12-18-2013|QA-Staff-12-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-11-2013|QA-Staff-12-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-04-2013|QA-Staff-12-04-2013]]<br />
*November<br />
**[[QA/StaffMeetings/QA-Staff-11-27-2013|QA-Staff-11-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-20-2013|QA-Staff-11-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-13-2013|QA-Staff-11-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-06-2013|QA-Staff-11-06-2013]]<br />
*October<br />
**[[QA/StaffMeetings/QA-Staff-10-30-2013|QA-Staff-10-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-23-2013|QA-Staff-10-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-16-2013|QA-Staff-10-16-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-09-2013|QA-Staff-10-09-2013]]<br />
*Sept<br />
**[[QA/StaffMeetings/QA-Staff-09-25-2013|QA-Staff-09-25-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-18-2013|QA-Staff-09-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-11-2013|QA-Staff-09-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-04-2013|QA-Staff-09-04-2013]]<br />
*August 2013<br />
**[[QA/StaffMeetings/QA-Staff-08-28-2013|QA-Staff-08-28-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-21-2013|QA-Staff-08-21-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-14-2013|QA-Staff-08-14-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-07-2013|QA-Staff-08-07-2013]]<br />
*July 2013<br />
**[[QA/StaffMeetings/QA-Staff-07-31-2013|QA-Staff-07-31-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-24-2013|QA-Staff-07-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-17-2013|QA-Staff-07-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-10-2013|QA-Staff-07-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-03-2013|QA-Staff-07-03-2013]]<br />
*June 2013<br />
**[[QA/StaffMeetings/QA-Staff-06-26-2013|QA-Staff-06-26-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-19-2013|QA-Staff-06-19-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-12-2013|QA-Staff-06-12-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-05-2013|QA-Staff-06-05-2013]]<br />
*May 2013<br />
**[[QA/StaffMeetings/QA-Staff-05-29-2013|QA-Staff-05-29-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-22-2013|QA-Staff-05-22-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-15-2013|QA-Staff-05-15-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-08-2013|QA-Staff-05-08-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-01-2013|QA-Staff-05-01-2013]]<br />
*April 2013<br />
**[[QA/StaffMeetings/QA-Staff-04-24-2013|QA-Staff-04-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-17-2013|QA-Staff-04-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-10-2013|QA-Staff-04-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-03-2013|QA-Staff-04-03-2013]]<br />
* March 2013<br />
**[[QA/StaffMeetings/QA-Staff-03-27-2013|QA-Staff-03-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-20-2013|QA-Staff-03-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-13-2013|QA-Staff-03-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-06-2013|QA-Staff-03-06-2013]]<br />
* Febuary 2013<br />
**[[QA/StaffMeetings/QA-Staff-02-27-2013|QA-Staff-02-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-20-2013|QA-Staff-02-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-13-2013|QA-Staff-02-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-06-2013|QA-Staff-02-06-2013]]<br />
* January 2013<br />
**[[QA/StaffMeetings/QA-Staff-01-30-2013|QA-Staff-01-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-23-2013|QA-Staff-01-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-16-2013|QA-Staff-01-16-2013]]<br />
|}<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2012<br />
|-<br />
|<br />
* December 2012<br />
**[[QA/StaffMeetings/QA-Staff-12-19-2012|QA-Staff-12-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-12-2012|QA-Staff-12-12-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-05-2012|QA-Staff-12-05-2012]]<br />
* November<br />
**[[QA/StaffMeetings/QA-Staff-11-28-2012|QA-Staff-11-28-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-21-2012|QA-Staff-11-21-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-14-2012|QA-Staff-11-14-2012]]<br />
** <br />
* October<br />
**[[QA/StaffMeetings/QA-Staff-10-24-2012|QA-Staff-10-24-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-17-2012|QA-Staff-10-17-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-10-2012|QA-Staff-10-10-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-03-2012|QA-Staff-10-03-2012]]<br />
* September<br />
**[[QA/StaffMeetings/QA-Staff-09-19-2012|QA-Staff-09-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-09-12-2012|QA-Staff-09-12-2012]]<br />
* August<br />
**[[QA/StaffMeetings/QA-Staff-08-29-2012|QA-Staff-08-29-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-22-2012|QA-Staff-08-22-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-15-2012|QA-Staff-08-15-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-08-2012|QA-Staff-08-08-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-01-2012|QA-Staff-08-01-2012]]<br />
<br />
* July<br />
**[[QA/StaffMeetings/QA-Staff-07-25-2012|QA-Staff-07-25-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-18-2012|QA-Staff-07-18-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-11-2012|QA-Staff-07-11-2012]]<br />
<br />
* June<br />
**[[QA/StaffMeetings/QA-Staff-06-27-2012|QA-Staff-06-27-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-20-2012|QA-Staff-06-20-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-13-2012|QA-Staff-06-13-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-06-2012|QA-Staff-06-06-2012]]<br />
<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-30-2012|QA-Staff-05-30-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-23-2012|QA-Staff-05-23-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-16-2012|QA-Staff-05-16-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-09-2012|QA-Staff-05-09-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-02-2012|QA-Staff-05-02-2012]]<br />
* April<br />
** [[QA/StaffMeetings/QA-Staff-04-25-2012|QA-Staff-04-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-18-2012|QA-Staff-04-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-11-2012|QA-Staff-04-11-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-04-2012|QA-Staff-04-04-2012]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-28-2012|QA-Staff-03-28-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-21-2012|QA-Staff-03-21-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-14-2012|QA-Staff-03-14-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-07-2012|QA-Staff-03-07-2012]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-29-2012|QA-Staff-02-29-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-22-2012|QA-Staff-02-22-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-15-2012|QA-Staff-02-15-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-08-2012|QA-Staff-02-08-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-01-2012|QA-Staff-02-01-2012]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-25-2012|QA-Staff-01-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-18-2012|QA-Staff-01-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-04-2012|QA-Staff-01-04-2012]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2011 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-07-2011|QA-Staff-12-07-2011]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-09-2011|QA-Staff-11-09-2011]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-12-2011|QA-Staff-10-12-2011]]<br />
* Sept<br />
** [[QA/StaffMeetings/QA-Staff-09-28-2011|QA-Staff-09-28-2011]]<br />
* August<br />
** [[QA/StaffMeetings/QA-Staff-08-03-2011|QA-Staff-08-03-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-17-2011|QA-Staff-08-17-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-31-2011|QA-Staff-08-31-2011]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-06-2011|QA-Staff-07-06-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-07-20-2011|QA-Staff-07-20-2011]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-08-2011|QA-Staff-06-08-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-06-22-2011|QA-Staff-06-22-2011]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-25-2011|QA-Staff-05-25-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-05-11-2011|QA-Staff-05-11-2011]]<br />
* Apr<br />
** [[QA/StaffMeetings/QA-Staff-04-27-2011|QA-Staff-04-27-2011]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-02-2011|QA-Staff-03-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-16-2011|QA-Staff-03-16-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-30-2011|QA-Staff-03-30-2011]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-02-2011|QA-Staff-02-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-02-16-2011|QA-Staff-02-16-2011]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-05-2011|QA-Staff-01-05-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-01-19-2011|QA-Staff-01-19-2011]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2010 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-08-2010|QA-Staff-12-08-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-12-22-2010|QA-Staff-12-22-2010]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-10-2010|QA-Staff-11-10-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-11-24-2010|QA-Staff-11-24-2010]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-13-2010|QA-Staff-10-13-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-10-27-2010|QA-Staff-10-27-2010]]<br />
* Sep<br />
** [[QA/StaffMeetings/QA-Staff-09-01-2010|QA-Staff-09-01-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-09-29-2010|QA-Staff-09-29-2010]]<br />
* Aug<br />
** [[QA/StaffMeetings/QA-Staff-08-04-2010|QA-Staff-08-04-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-08-18-2010|QA-Staff-08-18-2010]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-21-2010|QA-Staff-07-21-2010]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-09-2010|QA-Staff-06-09-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-06-23-2010|QA-Staff-06-23-2010]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-12-2010|QA-Staff-05-12-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-05-26-2010|QA-Staff-05-26-2010]]<br />
* Apr<br />
** [https://intranet.mozilla.org/QA-Staff-04-14-2010 QA-Staff-04-14-2010]<br />
** [[QA/StaffMeetings/QA-Staff-04-28-2010|QA-Staff-04-28-2010]]<br />
* Mar<br />
** [https://intranet.mozilla.org/QA-Staff-03-10-2010 QA-Staff-03-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-17-2010 QA-Staff-03-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-24-2010 QA-Staff-03-24-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-31-2010 QA-Staff-03-31-2010]<br />
* Feb<br />
** [https://intranet.mozilla.org/QA-Staff-02-03-2010 QA-Staff-02-03-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-10-2010 QA-Staff-02-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-17-2010 QA-Staff-02-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-24-2010 QA-Staff-02-24-2010]<br />
|}</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting&diff=1058379QA/Team Meeting2015-02-25T23:31:32Z<p>Ctalbert: </p>
<hr />
<div>Our every 2 week meeting is open to the public. You're welcome to join.<br />
<br />
== Meeting Details ==<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Angel conference room.<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23qa irc://irc.mozilla.org:6697/#qa]<br />
<br />
* Please see below for next meeting date and previous archived meetings<br />
* [[QA/Team_Meeting/QA_Team_Template|Team Meeting Template]]<br />
* [[QA/StaffMeetings/videos| Videos of meetings]]<br />
<createbox><br />
align=left<br />
type=create<br />
preload=QA/Team_Meeting/QA_Team_Template<br />
default={{#time: Y-m-d | wednesday}}<br />
prefix=QA/Team_Meeting/QA_Team_Meeting-<br />
</createbox><br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2015 <br />
|-<br />
|<br />
* February 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-03-04|All Quality Meeting Feb 25]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-02-18|All Quality Meeting Feb 18]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-02-04|All Quality Meeting Feb 4]]<br />
* January 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-21|All Quality Meeting Jan 21]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-14|All Quality Meeting Jan 14]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-07|All Quality Meeting Jan 7]]<br />
|}<br />
<br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2014 <br />
|-<br />
|<br />
* December 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-17|QA Team Meeting Dec 17]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-10|QA Team Meeting Dec 10]]<br />
* November 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-26|QA Team Meeting Nov 26]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-19|QA Team Meeting Nov 19]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-12|QA Team Meeting Nov 12]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-05|QA Team Meeting Nov 5]]<br />
* October 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-29|QA Team Meeting Oct 29]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-22|QA Team Meeting Oct 22]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-15|QA Team Meeting Oct 15]]<br />
** QA Team Meeting Oct 08 - CANCELED<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-01|QA Team Meeting Oct 01]]<br />
*September 2014<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-24 | QA Team Meeting Sept 24]]<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-17 | QA Team Meeting Sept 17]]<br />
**[[QA/Team_Meeting/QA-Team-2014-09-10 | QA Team Meeting Sept 10]]<br />
**[[QA/Team_Meeting/QA-Team-09-03-2014 | QA Team Meeting Sept 3]]<br />
*August 2014<br />
**[[QA/StaffMeetings/QA-Staff-08-27-2014|QA-Staff-08-27-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-20-2014|QA-Staff-08-20-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-13-2014|QA-Staff-08-13-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-06-2014|QA-Staff-08-06-2014]]<br />
*July 2014<br />
** Meeting on July 30 was canceled due to QA Work Week<br />
**[[QA/StaffMeetings/QA-Staff-07-23-2014|QA-Staff-07-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-16-2014|QA-Staff-07-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-09-2014|QA-Staff-07-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-02-2014|QA-Staff-07-02-2014]]<br />
*June 2014<br />
**[[QA/StaffMeetings/QA-Staff-06-25-2014|QA-Staff-06-25-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-18-2014|QA-Staff-06-18-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-11-2014|QA-Staff-06-11-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-04-2014|QA-Staff-06-04-2014]]<br />
*May 2014<br />
**[[QA/StaffMeetings/QA-Staff-05-28-2014|QA-Staff-05-28-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-21-2014|QA-Staff-05-21-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-14-2014|QA-Staff-05-14-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-07-2014|QA-Staff-05-07-2014]]<br />
*April 2014<br />
**[[QA/StaffMeetings/QA-Staff-04-30-2014|QA-Staff-04-30-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-23-2014|QA-Staff-04-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-16-2014|QA-Staff-04-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-09-2014|QA-Staff-04-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-02-2014|QA-Staff-04-02-2014]]<br />
*March 2014<br />
**[[QA/StaffMeetings/QA-Staff-03-26-2014|QA-Staff-03-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-19-2014|QA-Staff-03-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-12-2014|QA-Staff-03-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-05-2014|QA-Staff-03-05-2014]]<br />
*February 2014<br />
**[[QA/StaffMeetings/QA-Staff-02-26-2014|QA-Staff-02-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-19-2014|QA-Staff-02-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-12-2014|QA-Staff-02-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-05-2014|QA-Staff-02-05-2014]]<br />
*January 2014<br />
**[[QA/StaffMeetings/QA-Staff-01-29-2014|QA-Staff-01-29-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-22-2014|QA-Staff-01-22-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-15-2014|QA-Staff-01-15-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-08-2014|QA-Staff-01-08-2014]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2013<br />
|-<br />
|<br />
*December<br />
**[[QA/StaffMeetings/QA-Staff-12-18-2013|QA-Staff-12-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-11-2013|QA-Staff-12-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-04-2013|QA-Staff-12-04-2013]]<br />
*November<br />
**[[QA/StaffMeetings/QA-Staff-11-27-2013|QA-Staff-11-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-20-2013|QA-Staff-11-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-13-2013|QA-Staff-11-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-06-2013|QA-Staff-11-06-2013]]<br />
*October<br />
**[[QA/StaffMeetings/QA-Staff-10-30-2013|QA-Staff-10-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-23-2013|QA-Staff-10-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-16-2013|QA-Staff-10-16-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-09-2013|QA-Staff-10-09-2013]]<br />
*Sept<br />
**[[QA/StaffMeetings/QA-Staff-09-25-2013|QA-Staff-09-25-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-18-2013|QA-Staff-09-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-11-2013|QA-Staff-09-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-04-2013|QA-Staff-09-04-2013]]<br />
*August 2013<br />
**[[QA/StaffMeetings/QA-Staff-08-28-2013|QA-Staff-08-28-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-21-2013|QA-Staff-08-21-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-14-2013|QA-Staff-08-14-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-07-2013|QA-Staff-08-07-2013]]<br />
*July 2013<br />
**[[QA/StaffMeetings/QA-Staff-07-31-2013|QA-Staff-07-31-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-24-2013|QA-Staff-07-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-17-2013|QA-Staff-07-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-10-2013|QA-Staff-07-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-03-2013|QA-Staff-07-03-2013]]<br />
*June 2013<br />
**[[QA/StaffMeetings/QA-Staff-06-26-2013|QA-Staff-06-26-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-19-2013|QA-Staff-06-19-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-12-2013|QA-Staff-06-12-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-05-2013|QA-Staff-06-05-2013]]<br />
*May 2013<br />
**[[QA/StaffMeetings/QA-Staff-05-29-2013|QA-Staff-05-29-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-22-2013|QA-Staff-05-22-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-15-2013|QA-Staff-05-15-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-08-2013|QA-Staff-05-08-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-01-2013|QA-Staff-05-01-2013]]<br />
*April 2013<br />
**[[QA/StaffMeetings/QA-Staff-04-24-2013|QA-Staff-04-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-17-2013|QA-Staff-04-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-10-2013|QA-Staff-04-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-03-2013|QA-Staff-04-03-2013]]<br />
* March 2013<br />
**[[QA/StaffMeetings/QA-Staff-03-27-2013|QA-Staff-03-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-20-2013|QA-Staff-03-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-13-2013|QA-Staff-03-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-06-2013|QA-Staff-03-06-2013]]<br />
* Febuary 2013<br />
**[[QA/StaffMeetings/QA-Staff-02-27-2013|QA-Staff-02-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-20-2013|QA-Staff-02-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-13-2013|QA-Staff-02-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-06-2013|QA-Staff-02-06-2013]]<br />
* January 2013<br />
**[[QA/StaffMeetings/QA-Staff-01-30-2013|QA-Staff-01-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-23-2013|QA-Staff-01-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-16-2013|QA-Staff-01-16-2013]]<br />
|}<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2012<br />
|-<br />
|<br />
* December 2012<br />
**[[QA/StaffMeetings/QA-Staff-12-19-2012|QA-Staff-12-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-12-2012|QA-Staff-12-12-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-05-2012|QA-Staff-12-05-2012]]<br />
* November<br />
**[[QA/StaffMeetings/QA-Staff-11-28-2012|QA-Staff-11-28-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-21-2012|QA-Staff-11-21-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-14-2012|QA-Staff-11-14-2012]]<br />
** <br />
* October<br />
**[[QA/StaffMeetings/QA-Staff-10-24-2012|QA-Staff-10-24-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-17-2012|QA-Staff-10-17-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-10-2012|QA-Staff-10-10-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-03-2012|QA-Staff-10-03-2012]]<br />
* September<br />
**[[QA/StaffMeetings/QA-Staff-09-19-2012|QA-Staff-09-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-09-12-2012|QA-Staff-09-12-2012]]<br />
* August<br />
**[[QA/StaffMeetings/QA-Staff-08-29-2012|QA-Staff-08-29-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-22-2012|QA-Staff-08-22-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-15-2012|QA-Staff-08-15-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-08-2012|QA-Staff-08-08-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-01-2012|QA-Staff-08-01-2012]]<br />
<br />
* July<br />
**[[QA/StaffMeetings/QA-Staff-07-25-2012|QA-Staff-07-25-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-18-2012|QA-Staff-07-18-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-11-2012|QA-Staff-07-11-2012]]<br />
<br />
* June<br />
**[[QA/StaffMeetings/QA-Staff-06-27-2012|QA-Staff-06-27-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-20-2012|QA-Staff-06-20-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-13-2012|QA-Staff-06-13-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-06-2012|QA-Staff-06-06-2012]]<br />
<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-30-2012|QA-Staff-05-30-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-23-2012|QA-Staff-05-23-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-16-2012|QA-Staff-05-16-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-09-2012|QA-Staff-05-09-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-02-2012|QA-Staff-05-02-2012]]<br />
* April<br />
** [[QA/StaffMeetings/QA-Staff-04-25-2012|QA-Staff-04-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-18-2012|QA-Staff-04-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-11-2012|QA-Staff-04-11-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-04-2012|QA-Staff-04-04-2012]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-28-2012|QA-Staff-03-28-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-21-2012|QA-Staff-03-21-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-14-2012|QA-Staff-03-14-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-07-2012|QA-Staff-03-07-2012]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-29-2012|QA-Staff-02-29-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-22-2012|QA-Staff-02-22-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-15-2012|QA-Staff-02-15-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-08-2012|QA-Staff-02-08-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-01-2012|QA-Staff-02-01-2012]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-25-2012|QA-Staff-01-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-18-2012|QA-Staff-01-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-04-2012|QA-Staff-01-04-2012]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2011 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-07-2011|QA-Staff-12-07-2011]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-09-2011|QA-Staff-11-09-2011]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-12-2011|QA-Staff-10-12-2011]]<br />
* Sept<br />
** [[QA/StaffMeetings/QA-Staff-09-28-2011|QA-Staff-09-28-2011]]<br />
* August<br />
** [[QA/StaffMeetings/QA-Staff-08-03-2011|QA-Staff-08-03-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-17-2011|QA-Staff-08-17-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-31-2011|QA-Staff-08-31-2011]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-06-2011|QA-Staff-07-06-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-07-20-2011|QA-Staff-07-20-2011]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-08-2011|QA-Staff-06-08-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-06-22-2011|QA-Staff-06-22-2011]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-25-2011|QA-Staff-05-25-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-05-11-2011|QA-Staff-05-11-2011]]<br />
* Apr<br />
** [[QA/StaffMeetings/QA-Staff-04-27-2011|QA-Staff-04-27-2011]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-02-2011|QA-Staff-03-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-16-2011|QA-Staff-03-16-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-30-2011|QA-Staff-03-30-2011]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-02-2011|QA-Staff-02-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-02-16-2011|QA-Staff-02-16-2011]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-05-2011|QA-Staff-01-05-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-01-19-2011|QA-Staff-01-19-2011]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2010 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-08-2010|QA-Staff-12-08-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-12-22-2010|QA-Staff-12-22-2010]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-10-2010|QA-Staff-11-10-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-11-24-2010|QA-Staff-11-24-2010]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-13-2010|QA-Staff-10-13-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-10-27-2010|QA-Staff-10-27-2010]]<br />
* Sep<br />
** [[QA/StaffMeetings/QA-Staff-09-01-2010|QA-Staff-09-01-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-09-29-2010|QA-Staff-09-29-2010]]<br />
* Aug<br />
** [[QA/StaffMeetings/QA-Staff-08-04-2010|QA-Staff-08-04-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-08-18-2010|QA-Staff-08-18-2010]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-21-2010|QA-Staff-07-21-2010]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-09-2010|QA-Staff-06-09-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-06-23-2010|QA-Staff-06-23-2010]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-12-2010|QA-Staff-05-12-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-05-26-2010|QA-Staff-05-26-2010]]<br />
* Apr<br />
** [https://intranet.mozilla.org/QA-Staff-04-14-2010 QA-Staff-04-14-2010]<br />
** [[QA/StaffMeetings/QA-Staff-04-28-2010|QA-Staff-04-28-2010]]<br />
* Mar<br />
** [https://intranet.mozilla.org/QA-Staff-03-10-2010 QA-Staff-03-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-17-2010 QA-Staff-03-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-24-2010 QA-Staff-03-24-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-31-2010 QA-Staff-03-31-2010]<br />
* Feb<br />
** [https://intranet.mozilla.org/QA-Staff-02-03-2010 QA-Staff-02-03-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-10-2010 QA-Staff-02-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-17-2010 QA-Staff-02-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-24-2010 QA-Staff-02-24-2010]<br />
|}</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2015-03-04&diff=1058378QA/Team Meeting/QA Team Meeting-2015-03-042015-02-25T23:30:02Z<p>Ctalbert: Created page with "= Mozilla QA Meeting March 4, 2015 = # Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA # # Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SS..."</p>
<hr />
<div>= Mozilla QA Meeting March 4, 2015 =<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
<br />
== Actions From Last Week ==<br />
<br />
== Deadlines and Schedules ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
=== Other Notable Dates/Events (Read Only) ===<br />
*<br />
<br />
== Discussion & Updates for Team ==<br />
* <small>''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''</small><br />
* This meeting, going forward<br />
* Fx OS V3 idea announcement last week<br />
* QA Tea Time reminder - https://etherpad.mozilla.org/QA-tea-time<br />
<br />
== Lightning Talk ==<br />
* <small>''[[QA/Team_Meeting/Lightning Talk List|Lightning talk list]]''</small><br />
<br />
== Contributors ==<br />
=== New Contributor Spotlight ===<br />
These are new contributors, if you see them around, say hello<br />
*<br />
<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO (Read Only) ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Electrolysis&diff=1057083QA/Electrolysis2015-02-19T19:36:08Z<p>Ctalbert: /* Feb 19 - Feb 26 */</p>
<hr />
<div>{{TOC right}} <br />
This is the test plan for [[Electrolysis]], also referred to as the e10s project or "multiprocess". With e10s enabled, Firefox content runs in a different process than the browser itself. This will help improve performance and security. Our goals in testing are to identify and communicate problems, and to be able to give a recommendation for when e10s may be ready to stay on by default for non-Nightly channels. <br />
<br />
=People=<br />
* Juan Becerra - QA lead<br />
* Tracy Walker<br />
* [https://wiki.mozilla.org/Electrolysis#People e10s team]<br />
<br />
= Goal =<br />
Help E10S to achieve the same level of quality as non-e10s nightly Firefox by the time it goes to beta.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Define and establish baseline quality for e10s vs. non-e10s versions in terms of stability and memory footprint.<br />
# Identify and help triage bugs to address the quality gap<br />
# Define quality requirements for ship to aurora/dev edition<br />
# Work to identify areas of unknown bugs and risk by experimenting with expanding automated test coverage to previously untested platforms required for ship to aurora/dev edition.<br />
<br />
===How to test e10s===<br />
<br />
Please test e10s in [https://nightly.mozilla.org/ Nightly]. <br />
<br />
To enable e10s, check the "Enable e10s" or "multiprocess" box in about:preferences, and restart Nightly. <br />
If you have any problems or questions, drop by #e10s on IRC.<br />
<br />
; Reporting bugs<br />
When you find a problem, please report a bug. Please include the word "[e10s]" in the summary and set the "tracking-e10s" flag to '?' to ensure your bugs get triaged. (If you are certain a bug is present with e10s enabled, but not present with it turned off.)<br />
<br />
; Identifying e10s crashes<br />
Find and file e10s crashes by searching crash-stats for reports that include [https://crash-stats.mozilla.com/search/?dom_ipc_enabled=__true__&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform domipcenabled]. <br />
<br />
; Testing addons<br />
You can test popular addons from this list: http://arewee10syet.com<br />
<br />
==Status==<br />
===Milestones===<br />
Check the tracking-e10s field. ? means it needs triage.<br />
* Milestone 1: e10s is useable by average Nightly users. {{Bug|997456}}<br />
* m4: high priority, needs to be fixed asap<br />
* m6: blocking uplift to aurora.<br />
* m8: blocking uplift to beta. <br />
* +: tracking-e10s+ blocks uplift to release.<br />
* later: this bug has been triaged, and will not block release.<br />
<br />
;Releases<br />
Goals for releases so far:<br />
* Firefox 36: enable e10s by default in Nightly, then disabled in Aurora.<br />
* Firefox 37: (Nov. 24) e10s enabled by default in Nightly.<br />
* Firefox 38: This may end up being the target version for e10s to ride the trains to release.<br />
<br />
== Readiness ==<br />
Testing e10s really means testing all the functionality of Firefox. <br />
There are some key areas in a [https://wiki.mozilla.org/QA/Electrolysis/Feature_checklist feature checklist] where QA feature owners have expertise in testing, or where we think it will be useful to focus exploratory testing, along with our test coverage of each feature.<br />
Here are our current feature testing priorities. <br />
<br />
Current features to explore:<br />
* Developer Tools<br />
Do manual and exploratory testing. Report bugs, and associate them with the Dev Tools e10s tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=875871<br />
* Session store<br />
<br />
==Triage==<br />
The [[Electrolysis]] team meets regularly to triage bugs which are tagged ''tracking-e10s:?''. (TODO: add meeting times)<br />
<br />
* Top priority right now: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m4+]<br />
* These bugs block e10s moving to Aurora: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m6+]<br />
* These bugs block e10s moving to Beta: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=8 tracking-e10s:m8+]<br />
<br />
;Blocking Aurora ride (m4)<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,status,component,op_sys",<br />
"f1":"cf_tracking_e10s",<br />
"o1":"substring",<br />
"v1":"4"<br />
}<br />
</bugzilla><br />
<br />
==Triage incoming bugs to look for likely e10s issues==<br />
Once e10s is enabled by default on Nightly, we should see an influx of e10s bugs. <br />
<br />
How can we tell they may be e10s related? We will need to evaluate incoming bugs in Nightly with e10s turned on and turned off. Anything that is e10s related should get a whiteboard tag and we may also want to rate them for severity or mark them as blockers. We can ask bug reporters to check in about:support and search for the word "multiprocess" (which means e10s is on).<br />
<br />
If you are able to confirm a bug and can tell it is an e10s issue,<br />
please nominate the bug for the e10s tracking flag.<br />
<br />
Incoming bugs on Nightly 36, not marked with a tracking-e10s flag yet: https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591695&o1=isempty&o2=notsubstring&query_format=advanced&f2=short_desc&bug_status=UNCONFIRMED&bug_status=NEW&version=36%20Branch&version=36%20Branch&v2=intermittent&product=Core&product=Firefox&product=Toolkit<br />
<br />
==QA wanted==<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"whiteboard":"qawanted"<br />
}<br />
</bugzilla><br />
<br />
<br />
==Fixed bug triage==<br />
e10s bugs marked as RESOLVED FIXED. <br />
<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys,priority,severity,cf_qa_whiteboard",<br />
"resolution":"FIXED",<br />
"status":"RESOLVED",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"f1":"cf_qa_whiteboard",<br />
"o1":"nowords",<br />
"v1":"qa"<br />
}<br />
</bugzilla><br />
<br />
==2015 work==<br />
Q1 strategy and goals for QA: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
; e10s test metrics <br />
* Tests skipped in manifests: 225 skipped under e10s. 173 have bugs associated. <br />
* some mochitest-plain-e10s and mochitest-browser-chrome-e10s tests are enabled http://brasstacks.mozilla.com/testreports/weekly/2015-01-04.informant-report.html <br />
** mochitest-browser-chrome-e10s: linux-opt and linux64-opt have 58% of the bc tests enabled.<br />
** mochitest-plain-e10s: linux-debug: 79%. linux-opt: 80%. linux-64-debug: 79% linux64-opt: 80%<br />
* bug filed to turn more test "buckets" on for various platforms (that are green on [https://treeherder.mozilla.org/#/jobs?repo=holly holly] after a recent merge): https://bugzilla.mozilla.org/show_bug.cgi?id=1122901<br />
<br />
;Stability metrics.<br />
This is not as much of a problem as we thought it might be. Having e10s doesn't appear to be causing bad problems with crashes. <br />
* Current crash rate in Nightly. ''The crash rate for Nightly around Feb. 1 is at 10%. None of the top 10 crashes are e10s-specific. '' <br />
* Browser process crash rate: 100-500/week for each topcrash. Lower volume than content process crashes. <br />
* Content process crash rate: Most crashes with dom_ipc_enabled are content crashes. 300-3000/week for each topcrashers. https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=content&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature <br />
* (What % of this are startup crashes?) [https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=browser&uptime=%3C%3D1&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature browser]: very low. [https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=content&uptime=%3C%3D1&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature content]: currently still low <br />
* (Average uptime between crashes/ mean time between failure) <br />
* We want to aim for at least a 7-8% crash rate before moving to Aurora.<br />
* Could we get MTBF for non-e10s nightly (prior release, perhaps?), e10s enabled, and content crashes<br />
* Startup crashes as well.<br />
<br />
; Near Horizon Issues and Notes<br />
* Fixing crasher {{bug|1116884}} will increase stability in e10s.<br />
* There seems to be traction in platform bugs that are needed for developer tools compatibility in e10s<br />
** https://etherpad.mozilla.org/devtools-e10s-statuses<br />
* Add-on compatibility work is ongoing.<br />
* We still don't have a community onboarding story for e10s.<br />
* Current ship plan:<br />
** e10s in Aurora 39<br />
** e10s in Beta 40<br />
** e10s in Release 41 or later<br />
** (FYI: Firefox 42 is last release of 2015)<br />
<br />
= Sprint Notes =<br />
== Feb 19 - Feb 26 ==<br />
* [Juan] Followed up with Florin to prioritize session restore and tab browsing regression testing<br />
* [Juan] Will add a means to track results of that work<br />
* [Tracy] Dig into crash spike in nightly and make sure bugs are filed<br />
* [Juan] Follow up with releng about getting the automated tests turned on on central that are passing on holly.<br />
* [Juan & Tracy] Work on getting test day together for addons <br />
* [Tracy] continue investigating addon breakage<br />
* [clint] send Tracy and Juan a set of recent features that landed with known e10s deficiencies</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Electrolysis&diff=1057082QA/Electrolysis2015-02-19T19:35:24Z<p>Ctalbert: /* Feb 19 - Feb 26 */</p>
<hr />
<div>{{TOC right}} <br />
This is the test plan for [[Electrolysis]], also referred to as the e10s project or "multiprocess". With e10s enabled, Firefox content runs in a different process than the browser itself. This will help improve performance and security. Our goals in testing are to identify and communicate problems, and to be able to give a recommendation for when e10s may be ready to stay on by default for non-Nightly channels. <br />
<br />
=People=<br />
* Juan Becerra - QA lead<br />
* Tracy Walker<br />
* [https://wiki.mozilla.org/Electrolysis#People e10s team]<br />
<br />
= Goal =<br />
Help E10S to achieve the same level of quality as non-e10s nightly Firefox by the time it goes to beta.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Define and establish baseline quality for e10s vs. non-e10s versions in terms of stability and memory footprint.<br />
# Identify and help triage bugs to address the quality gap<br />
# Define quality requirements for ship to aurora/dev edition<br />
# Work to identify areas of unknown bugs and risk by experimenting with expanding automated test coverage to previously untested platforms required for ship to aurora/dev edition.<br />
<br />
===How to test e10s===<br />
<br />
Please test e10s in [https://nightly.mozilla.org/ Nightly]. <br />
<br />
To enable e10s, check the "Enable e10s" or "multiprocess" box in about:preferences, and restart Nightly. <br />
If you have any problems or questions, drop by #e10s on IRC.<br />
<br />
; Reporting bugs<br />
When you find a problem, please report a bug. Please include the word "[e10s]" in the summary and set the "tracking-e10s" flag to '?' to ensure your bugs get triaged. (If you are certain a bug is present with e10s enabled, but not present with it turned off.)<br />
<br />
; Identifying e10s crashes<br />
Find and file e10s crashes by searching crash-stats for reports that include [https://crash-stats.mozilla.com/search/?dom_ipc_enabled=__true__&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform domipcenabled]. <br />
<br />
; Testing addons<br />
You can test popular addons from this list: http://arewee10syet.com<br />
<br />
==Status==<br />
===Milestones===<br />
Check the tracking-e10s field. ? means it needs triage.<br />
* Milestone 1: e10s is useable by average Nightly users. {{Bug|997456}}<br />
* m4: high priority, needs to be fixed asap<br />
* m6: blocking uplift to aurora.<br />
* m8: blocking uplift to beta. <br />
* +: tracking-e10s+ blocks uplift to release.<br />
* later: this bug has been triaged, and will not block release.<br />
<br />
;Releases<br />
Goals for releases so far:<br />
* Firefox 36: enable e10s by default in Nightly, then disabled in Aurora.<br />
* Firefox 37: (Nov. 24) e10s enabled by default in Nightly.<br />
* Firefox 38: This may end up being the target version for e10s to ride the trains to release.<br />
<br />
== Readiness ==<br />
Testing e10s really means testing all the functionality of Firefox. <br />
There are some key areas in a [https://wiki.mozilla.org/QA/Electrolysis/Feature_checklist feature checklist] where QA feature owners have expertise in testing, or where we think it will be useful to focus exploratory testing, along with our test coverage of each feature.<br />
Here are our current feature testing priorities. <br />
<br />
Current features to explore:<br />
* Developer Tools<br />
Do manual and exploratory testing. Report bugs, and associate them with the Dev Tools e10s tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=875871<br />
* Session store<br />
<br />
==Triage==<br />
The [[Electrolysis]] team meets regularly to triage bugs which are tagged ''tracking-e10s:?''. (TODO: add meeting times)<br />
<br />
* Top priority right now: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m4+]<br />
* These bugs block e10s moving to Aurora: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m6+]<br />
* These bugs block e10s moving to Beta: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=8 tracking-e10s:m8+]<br />
<br />
;Blocking Aurora ride (m4)<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,status,component,op_sys",<br />
"f1":"cf_tracking_e10s",<br />
"o1":"substring",<br />
"v1":"4"<br />
}<br />
</bugzilla><br />
<br />
==Triage incoming bugs to look for likely e10s issues==<br />
Once e10s is enabled by default on Nightly, we should see an influx of e10s bugs. <br />
<br />
How can we tell they may be e10s related? We will need to evaluate incoming bugs in Nightly with e10s turned on and turned off. Anything that is e10s related should get a whiteboard tag and we may also want to rate them for severity or mark them as blockers. We can ask bug reporters to check in about:support and search for the word "multiprocess" (which means e10s is on).<br />
<br />
If you are able to confirm a bug and can tell it is an e10s issue,<br />
please nominate the bug for the e10s tracking flag.<br />
<br />
Incoming bugs on Nightly 36, not marked with a tracking-e10s flag yet: https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591695&o1=isempty&o2=notsubstring&query_format=advanced&f2=short_desc&bug_status=UNCONFIRMED&bug_status=NEW&version=36%20Branch&version=36%20Branch&v2=intermittent&product=Core&product=Firefox&product=Toolkit<br />
<br />
==QA wanted==<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"whiteboard":"qawanted"<br />
}<br />
</bugzilla><br />
<br />
<br />
==Fixed bug triage==<br />
e10s bugs marked as RESOLVED FIXED. <br />
<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys,priority,severity,cf_qa_whiteboard",<br />
"resolution":"FIXED",<br />
"status":"RESOLVED",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"f1":"cf_qa_whiteboard",<br />
"o1":"nowords",<br />
"v1":"qa"<br />
}<br />
</bugzilla><br />
<br />
==2015 work==<br />
Q1 strategy and goals for QA: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
; e10s test metrics <br />
* Tests skipped in manifests: 225 skipped under e10s. 173 have bugs associated. <br />
* some mochitest-plain-e10s and mochitest-browser-chrome-e10s tests are enabled http://brasstacks.mozilla.com/testreports/weekly/2015-01-04.informant-report.html <br />
** mochitest-browser-chrome-e10s: linux-opt and linux64-opt have 58% of the bc tests enabled.<br />
** mochitest-plain-e10s: linux-debug: 79%. linux-opt: 80%. linux-64-debug: 79% linux64-opt: 80%<br />
* bug filed to turn more test "buckets" on for various platforms (that are green on [https://treeherder.mozilla.org/#/jobs?repo=holly holly] after a recent merge): https://bugzilla.mozilla.org/show_bug.cgi?id=1122901<br />
<br />
;Stability metrics.<br />
This is not as much of a problem as we thought it might be. Having e10s doesn't appear to be causing bad problems with crashes. <br />
* Current crash rate in Nightly. ''The crash rate for Nightly around Feb. 1 is at 10%. None of the top 10 crashes are e10s-specific. '' <br />
* Browser process crash rate: 100-500/week for each topcrash. Lower volume than content process crashes. <br />
* Content process crash rate: Most crashes with dom_ipc_enabled are content crashes. 300-3000/week for each topcrashers. https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=content&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature <br />
* (What % of this are startup crashes?) [https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=browser&uptime=%3C%3D1&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature browser]: very low. [https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=content&uptime=%3C%3D1&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature content]: currently still low <br />
* (Average uptime between crashes/ mean time between failure) <br />
* We want to aim for at least a 7-8% crash rate before moving to Aurora.<br />
* Could we get MTBF for non-e10s nightly (prior release, perhaps?), e10s enabled, and content crashes<br />
* Startup crashes as well.<br />
<br />
; Near Horizon Issues and Notes<br />
* Fixing crasher {{bug|1116884}} will increase stability in e10s.<br />
* There seems to be traction in platform bugs that are needed for developer tools compatibility in e10s<br />
** https://etherpad.mozilla.org/devtools-e10s-statuses<br />
* Add-on compatibility work is ongoing.<br />
* We still don't have a community onboarding story for e10s.<br />
* Current ship plan:<br />
** e10s in Aurora 39<br />
** e10s in Beta 40<br />
** e10s in Release 41 or later<br />
** (FYI: Firefox 42 is last release of 2015)<br />
<br />
= Sprint Notes =<br />
== Feb 19 - Feb 26 ==<br />
* [Juan] Followed up with Florin to prioritize session restore and tab browsing regression testing<br />
* [Juan] Will add a means to track results of that work<br />
* [Tracy] Dig into crash spike in nightly and make sure bugs are filed<br />
* [Juan] Follow up with releng about getting the automated tests turned on on central that are passing on holly.<br />
* [Juan & Tracy] Work on getting test day together for addons <br />
* [Tracy] continue investigating addon breakage</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Electrolysis&diff=1057081QA/Electrolysis2015-02-19T19:33:07Z<p>Ctalbert: /* Feb 19 - Feb 26 */</p>
<hr />
<div>{{TOC right}} <br />
This is the test plan for [[Electrolysis]], also referred to as the e10s project or "multiprocess". With e10s enabled, Firefox content runs in a different process than the browser itself. This will help improve performance and security. Our goals in testing are to identify and communicate problems, and to be able to give a recommendation for when e10s may be ready to stay on by default for non-Nightly channels. <br />
<br />
=People=<br />
* Juan Becerra - QA lead<br />
* Tracy Walker<br />
* [https://wiki.mozilla.org/Electrolysis#People e10s team]<br />
<br />
= Goal =<br />
Help E10S to achieve the same level of quality as non-e10s nightly Firefox by the time it goes to beta.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Define and establish baseline quality for e10s vs. non-e10s versions in terms of stability and memory footprint.<br />
# Identify and help triage bugs to address the quality gap<br />
# Define quality requirements for ship to aurora/dev edition<br />
# Work to identify areas of unknown bugs and risk by experimenting with expanding automated test coverage to previously untested platforms required for ship to aurora/dev edition.<br />
<br />
===How to test e10s===<br />
<br />
Please test e10s in [https://nightly.mozilla.org/ Nightly]. <br />
<br />
To enable e10s, check the "Enable e10s" or "multiprocess" box in about:preferences, and restart Nightly. <br />
If you have any problems or questions, drop by #e10s on IRC.<br />
<br />
; Reporting bugs<br />
When you find a problem, please report a bug. Please include the word "[e10s]" in the summary and set the "tracking-e10s" flag to '?' to ensure your bugs get triaged. (If you are certain a bug is present with e10s enabled, but not present with it turned off.)<br />
<br />
; Identifying e10s crashes<br />
Find and file e10s crashes by searching crash-stats for reports that include [https://crash-stats.mozilla.com/search/?dom_ipc_enabled=__true__&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform domipcenabled]. <br />
<br />
; Testing addons<br />
You can test popular addons from this list: http://arewee10syet.com<br />
<br />
==Status==<br />
===Milestones===<br />
Check the tracking-e10s field. ? means it needs triage.<br />
* Milestone 1: e10s is useable by average Nightly users. {{Bug|997456}}<br />
* m4: high priority, needs to be fixed asap<br />
* m6: blocking uplift to aurora.<br />
* m8: blocking uplift to beta. <br />
* +: tracking-e10s+ blocks uplift to release.<br />
* later: this bug has been triaged, and will not block release.<br />
<br />
;Releases<br />
Goals for releases so far:<br />
* Firefox 36: enable e10s by default in Nightly, then disabled in Aurora.<br />
* Firefox 37: (Nov. 24) e10s enabled by default in Nightly.<br />
* Firefox 38: This may end up being the target version for e10s to ride the trains to release.<br />
<br />
== Readiness ==<br />
Testing e10s really means testing all the functionality of Firefox. <br />
There are some key areas in a [https://wiki.mozilla.org/QA/Electrolysis/Feature_checklist feature checklist] where QA feature owners have expertise in testing, or where we think it will be useful to focus exploratory testing, along with our test coverage of each feature.<br />
Here are our current feature testing priorities. <br />
<br />
Current features to explore:<br />
* Developer Tools<br />
Do manual and exploratory testing. Report bugs, and associate them with the Dev Tools e10s tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=875871<br />
* Session store<br />
<br />
==Triage==<br />
The [[Electrolysis]] team meets regularly to triage bugs which are tagged ''tracking-e10s:?''. (TODO: add meeting times)<br />
<br />
* Top priority right now: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m4+]<br />
* These bugs block e10s moving to Aurora: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m6+]<br />
* These bugs block e10s moving to Beta: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=8 tracking-e10s:m8+]<br />
<br />
;Blocking Aurora ride (m4)<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,status,component,op_sys",<br />
"f1":"cf_tracking_e10s",<br />
"o1":"substring",<br />
"v1":"4"<br />
}<br />
</bugzilla><br />
<br />
==Triage incoming bugs to look for likely e10s issues==<br />
Once e10s is enabled by default on Nightly, we should see an influx of e10s bugs. <br />
<br />
How can we tell they may be e10s related? We will need to evaluate incoming bugs in Nightly with e10s turned on and turned off. Anything that is e10s related should get a whiteboard tag and we may also want to rate them for severity or mark them as blockers. We can ask bug reporters to check in about:support and search for the word "multiprocess" (which means e10s is on).<br />
<br />
If you are able to confirm a bug and can tell it is an e10s issue,<br />
please nominate the bug for the e10s tracking flag.<br />
<br />
Incoming bugs on Nightly 36, not marked with a tracking-e10s flag yet: https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591695&o1=isempty&o2=notsubstring&query_format=advanced&f2=short_desc&bug_status=UNCONFIRMED&bug_status=NEW&version=36%20Branch&version=36%20Branch&v2=intermittent&product=Core&product=Firefox&product=Toolkit<br />
<br />
==QA wanted==<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"whiteboard":"qawanted"<br />
}<br />
</bugzilla><br />
<br />
<br />
==Fixed bug triage==<br />
e10s bugs marked as RESOLVED FIXED. <br />
<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys,priority,severity,cf_qa_whiteboard",<br />
"resolution":"FIXED",<br />
"status":"RESOLVED",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"f1":"cf_qa_whiteboard",<br />
"o1":"nowords",<br />
"v1":"qa"<br />
}<br />
</bugzilla><br />
<br />
==2015 work==<br />
Q1 strategy and goals for QA: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
; e10s test metrics <br />
* Tests skipped in manifests: 225 skipped under e10s. 173 have bugs associated. <br />
* some mochitest-plain-e10s and mochitest-browser-chrome-e10s tests are enabled http://brasstacks.mozilla.com/testreports/weekly/2015-01-04.informant-report.html <br />
** mochitest-browser-chrome-e10s: linux-opt and linux64-opt have 58% of the bc tests enabled.<br />
** mochitest-plain-e10s: linux-debug: 79%. linux-opt: 80%. linux-64-debug: 79% linux64-opt: 80%<br />
* bug filed to turn more test "buckets" on for various platforms (that are green on [https://treeherder.mozilla.org/#/jobs?repo=holly holly] after a recent merge): https://bugzilla.mozilla.org/show_bug.cgi?id=1122901<br />
<br />
;Stability metrics.<br />
This is not as much of a problem as we thought it might be. Having e10s doesn't appear to be causing bad problems with crashes. <br />
* Current crash rate in Nightly. ''The crash rate for Nightly around Feb. 1 is at 10%. None of the top 10 crashes are e10s-specific. '' <br />
* Browser process crash rate: 100-500/week for each topcrash. Lower volume than content process crashes. <br />
* Content process crash rate: Most crashes with dom_ipc_enabled are content crashes. 300-3000/week for each topcrashers. https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=content&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature <br />
* (What % of this are startup crashes?) [https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=browser&uptime=%3C%3D1&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature browser]: very low. [https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=content&uptime=%3C%3D1&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature content]: currently still low <br />
* (Average uptime between crashes/ mean time between failure) <br />
* We want to aim for at least a 7-8% crash rate before moving to Aurora.<br />
* Could we get MTBF for non-e10s nightly (prior release, perhaps?), e10s enabled, and content crashes<br />
* Startup crashes as well.<br />
<br />
; Near Horizon Issues and Notes<br />
* Fixing crasher {{bug|1116884}} will increase stability in e10s.<br />
* There seems to be traction in platform bugs that are needed for developer tools compatibility in e10s<br />
** https://etherpad.mozilla.org/devtools-e10s-statuses<br />
* Add-on compatibility work is ongoing.<br />
* We still don't have a community onboarding story for e10s.<br />
* Current ship plan:<br />
** e10s in Aurora 39<br />
** e10s in Beta 40<br />
** e10s in Release 41 or later<br />
** (FYI: Firefox 42 is last release of 2015)<br />
<br />
= Sprint Notes =<br />
== Feb 19 - Feb 26 ==<br />
* [Juan] Followed up with Florin to prioritize session restore and tab browsing regression testing<br />
* [Juan] Will add a means to track results of that work<br />
* [Tracy] Helping with tab browsing - tab tearing testing, analyzing what has recently changed that might not work with E10s<br />
* [Tracy] Dig into crash spike in nightly and make sure bugs are filed<br />
* [Juan] Follow up with releng about getting the automated tests turned on on central that are passing on holly.<br />
* [Juan & Tracy] Work on getting test day together for addons <br />
* [Tracy] continue investigating addon breakage</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Electrolysis&diff=1057080QA/Electrolysis2015-02-19T19:31:48Z<p>Ctalbert: </p>
<hr />
<div>{{TOC right}} <br />
This is the test plan for [[Electrolysis]], also referred to as the e10s project or "multiprocess". With e10s enabled, Firefox content runs in a different process than the browser itself. This will help improve performance and security. Our goals in testing are to identify and communicate problems, and to be able to give a recommendation for when e10s may be ready to stay on by default for non-Nightly channels. <br />
<br />
=People=<br />
* Juan Becerra - QA lead<br />
* Tracy Walker<br />
* [https://wiki.mozilla.org/Electrolysis#People e10s team]<br />
<br />
= Goal =<br />
Help E10S to achieve the same level of quality as non-e10s nightly Firefox by the time it goes to beta.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Define and establish baseline quality for e10s vs. non-e10s versions in terms of stability and memory footprint.<br />
# Identify and help triage bugs to address the quality gap<br />
# Define quality requirements for ship to aurora/dev edition<br />
# Work to identify areas of unknown bugs and risk by experimenting with expanding automated test coverage to previously untested platforms required for ship to aurora/dev edition.<br />
<br />
===How to test e10s===<br />
<br />
Please test e10s in [https://nightly.mozilla.org/ Nightly]. <br />
<br />
To enable e10s, check the "Enable e10s" or "multiprocess" box in about:preferences, and restart Nightly. <br />
If you have any problems or questions, drop by #e10s on IRC.<br />
<br />
; Reporting bugs<br />
When you find a problem, please report a bug. Please include the word "[e10s]" in the summary and set the "tracking-e10s" flag to '?' to ensure your bugs get triaged. (If you are certain a bug is present with e10s enabled, but not present with it turned off.)<br />
<br />
; Identifying e10s crashes<br />
Find and file e10s crashes by searching crash-stats for reports that include [https://crash-stats.mozilla.com/search/?dom_ipc_enabled=__true__&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform domipcenabled]. <br />
<br />
; Testing addons<br />
You can test popular addons from this list: http://arewee10syet.com<br />
<br />
==Status==<br />
===Milestones===<br />
Check the tracking-e10s field. ? means it needs triage.<br />
* Milestone 1: e10s is useable by average Nightly users. {{Bug|997456}}<br />
* m4: high priority, needs to be fixed asap<br />
* m6: blocking uplift to aurora.<br />
* m8: blocking uplift to beta. <br />
* +: tracking-e10s+ blocks uplift to release.<br />
* later: this bug has been triaged, and will not block release.<br />
<br />
;Releases<br />
Goals for releases so far:<br />
* Firefox 36: enable e10s by default in Nightly, then disabled in Aurora.<br />
* Firefox 37: (Nov. 24) e10s enabled by default in Nightly.<br />
* Firefox 38: This may end up being the target version for e10s to ride the trains to release.<br />
<br />
== Readiness ==<br />
Testing e10s really means testing all the functionality of Firefox. <br />
There are some key areas in a [https://wiki.mozilla.org/QA/Electrolysis/Feature_checklist feature checklist] where QA feature owners have expertise in testing, or where we think it will be useful to focus exploratory testing, along with our test coverage of each feature.<br />
Here are our current feature testing priorities. <br />
<br />
Current features to explore:<br />
* Developer Tools<br />
Do manual and exploratory testing. Report bugs, and associate them with the Dev Tools e10s tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=875871<br />
* Session store<br />
<br />
==Triage==<br />
The [[Electrolysis]] team meets regularly to triage bugs which are tagged ''tracking-e10s:?''. (TODO: add meeting times)<br />
<br />
* Top priority right now: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m4+]<br />
* These bugs block e10s moving to Aurora: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m6+]<br />
* These bugs block e10s moving to Beta: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=8 tracking-e10s:m8+]<br />
<br />
;Blocking Aurora ride (m4)<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,status,component,op_sys",<br />
"f1":"cf_tracking_e10s",<br />
"o1":"substring",<br />
"v1":"4"<br />
}<br />
</bugzilla><br />
<br />
==Triage incoming bugs to look for likely e10s issues==<br />
Once e10s is enabled by default on Nightly, we should see an influx of e10s bugs. <br />
<br />
How can we tell they may be e10s related? We will need to evaluate incoming bugs in Nightly with e10s turned on and turned off. Anything that is e10s related should get a whiteboard tag and we may also want to rate them for severity or mark them as blockers. We can ask bug reporters to check in about:support and search for the word "multiprocess" (which means e10s is on).<br />
<br />
If you are able to confirm a bug and can tell it is an e10s issue,<br />
please nominate the bug for the e10s tracking flag.<br />
<br />
Incoming bugs on Nightly 36, not marked with a tracking-e10s flag yet: https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591695&o1=isempty&o2=notsubstring&query_format=advanced&f2=short_desc&bug_status=UNCONFIRMED&bug_status=NEW&version=36%20Branch&version=36%20Branch&v2=intermittent&product=Core&product=Firefox&product=Toolkit<br />
<br />
==QA wanted==<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"whiteboard":"qawanted"<br />
}<br />
</bugzilla><br />
<br />
<br />
==Fixed bug triage==<br />
e10s bugs marked as RESOLVED FIXED. <br />
<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys,priority,severity,cf_qa_whiteboard",<br />
"resolution":"FIXED",<br />
"status":"RESOLVED",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"f1":"cf_qa_whiteboard",<br />
"o1":"nowords",<br />
"v1":"qa"<br />
}<br />
</bugzilla><br />
<br />
==2015 work==<br />
Q1 strategy and goals for QA: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
; e10s test metrics <br />
* Tests skipped in manifests: 225 skipped under e10s. 173 have bugs associated. <br />
* some mochitest-plain-e10s and mochitest-browser-chrome-e10s tests are enabled http://brasstacks.mozilla.com/testreports/weekly/2015-01-04.informant-report.html <br />
** mochitest-browser-chrome-e10s: linux-opt and linux64-opt have 58% of the bc tests enabled.<br />
** mochitest-plain-e10s: linux-debug: 79%. linux-opt: 80%. linux-64-debug: 79% linux64-opt: 80%<br />
* bug filed to turn more test "buckets" on for various platforms (that are green on [https://treeherder.mozilla.org/#/jobs?repo=holly holly] after a recent merge): https://bugzilla.mozilla.org/show_bug.cgi?id=1122901<br />
<br />
;Stability metrics.<br />
This is not as much of a problem as we thought it might be. Having e10s doesn't appear to be causing bad problems with crashes. <br />
* Current crash rate in Nightly. ''The crash rate for Nightly around Feb. 1 is at 10%. None of the top 10 crashes are e10s-specific. '' <br />
* Browser process crash rate: 100-500/week for each topcrash. Lower volume than content process crashes. <br />
* Content process crash rate: Most crashes with dom_ipc_enabled are content crashes. 300-3000/week for each topcrashers. https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=content&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature <br />
* (What % of this are startup crashes?) [https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=browser&uptime=%3C%3D1&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature browser]: very low. [https://crash-stats.mozilla.com/search/?product=Firefox&version=38.0a1&dom_ipc_enabled=!__null__&process_type=content&uptime=%3C%3D1&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature content]: currently still low <br />
* (Average uptime between crashes/ mean time between failure) <br />
* We want to aim for at least a 7-8% crash rate before moving to Aurora.<br />
* Could we get MTBF for non-e10s nightly (prior release, perhaps?), e10s enabled, and content crashes<br />
* Startup crashes as well.<br />
<br />
; Near Horizon Issues and Notes<br />
* Fixing crasher {{bug|1116884}} will increase stability in e10s.<br />
* There seems to be traction in platform bugs that are needed for developer tools compatibility in e10s<br />
** https://etherpad.mozilla.org/devtools-e10s-statuses<br />
* Add-on compatibility work is ongoing.<br />
* We still don't have a community onboarding story for e10s.<br />
* Current ship plan:<br />
** e10s in Aurora 39<br />
** e10s in Beta 40<br />
** e10s in Release 41 or later<br />
** (FYI: Firefox 42 is last release of 2015)<br />
<br />
= Sprint Notes =<br />
== Feb 19 - Feb 26 ==<br />
* [Juan] Followed up with Florin to prioritize session restore and tab browsing regression testing<br />
* [Juan] Will add a means to track results of that work<br />
* [Tracy] Helping with tab browsing - tab tearing testing, analyzing what has recently changed that might not work with E10s<br />
* [Tracy] Dig into crash spike in nightly and make sure bugs are filed<br />
* [Juan] Follow up with releng about getting the automated tests turned on on central that are passing on holly.</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2015-02-18&diff=1056849QA/Team Meeting/QA Team Meeting-2015-02-182015-02-18T20:01:22Z<p>Ctalbert: /* Discussion & Updates for Team */</p>
<hr />
<div>= Mozilla QA Meeting Feb 18 2015 =<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
<br />
== Actions From Last Week ==<br />
<br />
== Deadlines and Schedules ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
=== Other Notable Dates/Events (Read Only) ===<br />
*<br />
<br />
== Discussion & Updates for Team ==<br />
* <small>''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''</small><br />
* Release next week<br />
* Flash stuff, Reading List, Hello Screen Sharing<br />
<br />
== Lightning Talk ==<br />
* <small>''[[QA/Team_Meeting/Lightning Talk List|Lightning talk list]]''</small><br />
* Rebecca will talk about the OPW program today<br />
<br />
== Contributors ==<br />
=== New Contributor Spotlight ===<br />
These are new contributors, if you see them around, say hello<br />
*<br />
<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO (Read Only) ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2015-02-18&diff=1056848QA/Team Meeting/QA Team Meeting-2015-02-182015-02-18T20:00:26Z<p>Ctalbert: /* Lightning Talk */</p>
<hr />
<div>= Mozilla QA Meeting Feb 18 2015 =<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
<br />
== Actions From Last Week ==<br />
<br />
== Deadlines and Schedules ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
=== Other Notable Dates/Events (Read Only) ===<br />
*<br />
<br />
== Discussion & Updates for Team ==<br />
* <small>''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''</small><br />
<br />
== Lightning Talk ==<br />
* <small>''[[QA/Team_Meeting/Lightning Talk List|Lightning talk list]]''</small><br />
* Rebecca will talk about the OPW program today<br />
<br />
== Contributors ==<br />
=== New Contributor Spotlight ===<br />
These are new contributors, if you see them around, say hello<br />
*<br />
<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO (Read Only) ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting&diff=1056846QA/Team Meeting2015-02-18T19:59:28Z<p>Ctalbert: </p>
<hr />
<div>Our every 2 week meeting is open to the public. You're welcome to join.<br />
<br />
== Meeting Details ==<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Angel conference room.<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23qa irc://irc.mozilla.org:6697/#qa]<br />
<br />
* Please see below for next meeting date and previous archived meetings<br />
* [[QA/Team_Meeting/QA_Team_Template|Team Meeting Template]]<br />
* [[QA/StaffMeetings/videos| Videos of meetings]]<br />
<createbox><br />
align=left<br />
type=create<br />
preload=QA/Team_Meeting/QA_Team_Template<br />
default={{#time: Y-m-d | wednesday}}<br />
prefix=QA/Team_Meeting/QA_Team_Meeting-<br />
</createbox><br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2015 <br />
|-<br />
|<br />
* February 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-02-18|QA Team Meeting Feb 18]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-02-04|QA Team Meeting Feb 4]]<br />
* January 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-21|QA Team Meeting Jan 21]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-14|QA Team Meeting Jan 14]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-07|QA Team Meeting Jan 7]]<br />
|}<br />
<br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2014 <br />
|-<br />
|<br />
* December 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-17|QA Team Meeting Dec 17]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-10|QA Team Meeting Dec 10]]<br />
* November 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-26|QA Team Meeting Nov 26]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-19|QA Team Meeting Nov 19]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-12|QA Team Meeting Nov 12]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-05|QA Team Meeting Nov 5]]<br />
* October 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-29|QA Team Meeting Oct 29]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-22|QA Team Meeting Oct 22]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-15|QA Team Meeting Oct 15]]<br />
** QA Team Meeting Oct 08 - CANCELED<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-01|QA Team Meeting Oct 01]]<br />
*September 2014<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-24 | QA Team Meeting Sept 24]]<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-17 | QA Team Meeting Sept 17]]<br />
**[[QA/Team_Meeting/QA-Team-2014-09-10 | QA Team Meeting Sept 10]]<br />
**[[QA/Team_Meeting/QA-Team-09-03-2014 | QA Team Meeting Sept 3]]<br />
*August 2014<br />
**[[QA/StaffMeetings/QA-Staff-08-27-2014|QA-Staff-08-27-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-20-2014|QA-Staff-08-20-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-13-2014|QA-Staff-08-13-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-06-2014|QA-Staff-08-06-2014]]<br />
*July 2014<br />
** Meeting on July 30 was canceled due to QA Work Week<br />
**[[QA/StaffMeetings/QA-Staff-07-23-2014|QA-Staff-07-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-16-2014|QA-Staff-07-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-09-2014|QA-Staff-07-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-02-2014|QA-Staff-07-02-2014]]<br />
*June 2014<br />
**[[QA/StaffMeetings/QA-Staff-06-25-2014|QA-Staff-06-25-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-18-2014|QA-Staff-06-18-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-11-2014|QA-Staff-06-11-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-04-2014|QA-Staff-06-04-2014]]<br />
*May 2014<br />
**[[QA/StaffMeetings/QA-Staff-05-28-2014|QA-Staff-05-28-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-21-2014|QA-Staff-05-21-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-14-2014|QA-Staff-05-14-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-07-2014|QA-Staff-05-07-2014]]<br />
*April 2014<br />
**[[QA/StaffMeetings/QA-Staff-04-30-2014|QA-Staff-04-30-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-23-2014|QA-Staff-04-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-16-2014|QA-Staff-04-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-09-2014|QA-Staff-04-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-02-2014|QA-Staff-04-02-2014]]<br />
*March 2014<br />
**[[QA/StaffMeetings/QA-Staff-03-26-2014|QA-Staff-03-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-19-2014|QA-Staff-03-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-12-2014|QA-Staff-03-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-05-2014|QA-Staff-03-05-2014]]<br />
*February 2014<br />
**[[QA/StaffMeetings/QA-Staff-02-26-2014|QA-Staff-02-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-19-2014|QA-Staff-02-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-12-2014|QA-Staff-02-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-05-2014|QA-Staff-02-05-2014]]<br />
*January 2014<br />
**[[QA/StaffMeetings/QA-Staff-01-29-2014|QA-Staff-01-29-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-22-2014|QA-Staff-01-22-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-15-2014|QA-Staff-01-15-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-08-2014|QA-Staff-01-08-2014]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2013<br />
|-<br />
|<br />
*December<br />
**[[QA/StaffMeetings/QA-Staff-12-18-2013|QA-Staff-12-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-11-2013|QA-Staff-12-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-04-2013|QA-Staff-12-04-2013]]<br />
*November<br />
**[[QA/StaffMeetings/QA-Staff-11-27-2013|QA-Staff-11-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-20-2013|QA-Staff-11-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-13-2013|QA-Staff-11-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-06-2013|QA-Staff-11-06-2013]]<br />
*October<br />
**[[QA/StaffMeetings/QA-Staff-10-30-2013|QA-Staff-10-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-23-2013|QA-Staff-10-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-16-2013|QA-Staff-10-16-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-09-2013|QA-Staff-10-09-2013]]<br />
*Sept<br />
**[[QA/StaffMeetings/QA-Staff-09-25-2013|QA-Staff-09-25-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-18-2013|QA-Staff-09-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-11-2013|QA-Staff-09-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-04-2013|QA-Staff-09-04-2013]]<br />
*August 2013<br />
**[[QA/StaffMeetings/QA-Staff-08-28-2013|QA-Staff-08-28-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-21-2013|QA-Staff-08-21-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-14-2013|QA-Staff-08-14-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-07-2013|QA-Staff-08-07-2013]]<br />
*July 2013<br />
**[[QA/StaffMeetings/QA-Staff-07-31-2013|QA-Staff-07-31-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-24-2013|QA-Staff-07-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-17-2013|QA-Staff-07-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-10-2013|QA-Staff-07-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-03-2013|QA-Staff-07-03-2013]]<br />
*June 2013<br />
**[[QA/StaffMeetings/QA-Staff-06-26-2013|QA-Staff-06-26-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-19-2013|QA-Staff-06-19-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-12-2013|QA-Staff-06-12-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-05-2013|QA-Staff-06-05-2013]]<br />
*May 2013<br />
**[[QA/StaffMeetings/QA-Staff-05-29-2013|QA-Staff-05-29-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-22-2013|QA-Staff-05-22-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-15-2013|QA-Staff-05-15-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-08-2013|QA-Staff-05-08-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-01-2013|QA-Staff-05-01-2013]]<br />
*April 2013<br />
**[[QA/StaffMeetings/QA-Staff-04-24-2013|QA-Staff-04-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-17-2013|QA-Staff-04-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-10-2013|QA-Staff-04-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-03-2013|QA-Staff-04-03-2013]]<br />
* March 2013<br />
**[[QA/StaffMeetings/QA-Staff-03-27-2013|QA-Staff-03-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-20-2013|QA-Staff-03-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-13-2013|QA-Staff-03-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-06-2013|QA-Staff-03-06-2013]]<br />
* Febuary 2013<br />
**[[QA/StaffMeetings/QA-Staff-02-27-2013|QA-Staff-02-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-20-2013|QA-Staff-02-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-13-2013|QA-Staff-02-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-06-2013|QA-Staff-02-06-2013]]<br />
* January 2013<br />
**[[QA/StaffMeetings/QA-Staff-01-30-2013|QA-Staff-01-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-23-2013|QA-Staff-01-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-16-2013|QA-Staff-01-16-2013]]<br />
|}<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2012<br />
|-<br />
|<br />
* December 2012<br />
**[[QA/StaffMeetings/QA-Staff-12-19-2012|QA-Staff-12-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-12-2012|QA-Staff-12-12-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-05-2012|QA-Staff-12-05-2012]]<br />
* November<br />
**[[QA/StaffMeetings/QA-Staff-11-28-2012|QA-Staff-11-28-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-21-2012|QA-Staff-11-21-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-14-2012|QA-Staff-11-14-2012]]<br />
** <br />
* October<br />
**[[QA/StaffMeetings/QA-Staff-10-24-2012|QA-Staff-10-24-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-17-2012|QA-Staff-10-17-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-10-2012|QA-Staff-10-10-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-03-2012|QA-Staff-10-03-2012]]<br />
* September<br />
**[[QA/StaffMeetings/QA-Staff-09-19-2012|QA-Staff-09-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-09-12-2012|QA-Staff-09-12-2012]]<br />
* August<br />
**[[QA/StaffMeetings/QA-Staff-08-29-2012|QA-Staff-08-29-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-22-2012|QA-Staff-08-22-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-15-2012|QA-Staff-08-15-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-08-2012|QA-Staff-08-08-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-01-2012|QA-Staff-08-01-2012]]<br />
<br />
* July<br />
**[[QA/StaffMeetings/QA-Staff-07-25-2012|QA-Staff-07-25-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-18-2012|QA-Staff-07-18-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-11-2012|QA-Staff-07-11-2012]]<br />
<br />
* June<br />
**[[QA/StaffMeetings/QA-Staff-06-27-2012|QA-Staff-06-27-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-20-2012|QA-Staff-06-20-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-13-2012|QA-Staff-06-13-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-06-2012|QA-Staff-06-06-2012]]<br />
<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-30-2012|QA-Staff-05-30-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-23-2012|QA-Staff-05-23-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-16-2012|QA-Staff-05-16-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-09-2012|QA-Staff-05-09-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-02-2012|QA-Staff-05-02-2012]]<br />
* April<br />
** [[QA/StaffMeetings/QA-Staff-04-25-2012|QA-Staff-04-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-18-2012|QA-Staff-04-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-11-2012|QA-Staff-04-11-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-04-2012|QA-Staff-04-04-2012]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-28-2012|QA-Staff-03-28-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-21-2012|QA-Staff-03-21-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-14-2012|QA-Staff-03-14-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-07-2012|QA-Staff-03-07-2012]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-29-2012|QA-Staff-02-29-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-22-2012|QA-Staff-02-22-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-15-2012|QA-Staff-02-15-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-08-2012|QA-Staff-02-08-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-01-2012|QA-Staff-02-01-2012]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-25-2012|QA-Staff-01-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-18-2012|QA-Staff-01-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-04-2012|QA-Staff-01-04-2012]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2011 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-07-2011|QA-Staff-12-07-2011]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-09-2011|QA-Staff-11-09-2011]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-12-2011|QA-Staff-10-12-2011]]<br />
* Sept<br />
** [[QA/StaffMeetings/QA-Staff-09-28-2011|QA-Staff-09-28-2011]]<br />
* August<br />
** [[QA/StaffMeetings/QA-Staff-08-03-2011|QA-Staff-08-03-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-17-2011|QA-Staff-08-17-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-31-2011|QA-Staff-08-31-2011]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-06-2011|QA-Staff-07-06-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-07-20-2011|QA-Staff-07-20-2011]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-08-2011|QA-Staff-06-08-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-06-22-2011|QA-Staff-06-22-2011]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-25-2011|QA-Staff-05-25-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-05-11-2011|QA-Staff-05-11-2011]]<br />
* Apr<br />
** [[QA/StaffMeetings/QA-Staff-04-27-2011|QA-Staff-04-27-2011]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-02-2011|QA-Staff-03-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-16-2011|QA-Staff-03-16-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-30-2011|QA-Staff-03-30-2011]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-02-2011|QA-Staff-02-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-02-16-2011|QA-Staff-02-16-2011]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-05-2011|QA-Staff-01-05-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-01-19-2011|QA-Staff-01-19-2011]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2010 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-08-2010|QA-Staff-12-08-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-12-22-2010|QA-Staff-12-22-2010]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-10-2010|QA-Staff-11-10-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-11-24-2010|QA-Staff-11-24-2010]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-13-2010|QA-Staff-10-13-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-10-27-2010|QA-Staff-10-27-2010]]<br />
* Sep<br />
** [[QA/StaffMeetings/QA-Staff-09-01-2010|QA-Staff-09-01-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-09-29-2010|QA-Staff-09-29-2010]]<br />
* Aug<br />
** [[QA/StaffMeetings/QA-Staff-08-04-2010|QA-Staff-08-04-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-08-18-2010|QA-Staff-08-18-2010]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-21-2010|QA-Staff-07-21-2010]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-09-2010|QA-Staff-06-09-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-06-23-2010|QA-Staff-06-23-2010]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-12-2010|QA-Staff-05-12-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-05-26-2010|QA-Staff-05-26-2010]]<br />
* Apr<br />
** [https://intranet.mozilla.org/QA-Staff-04-14-2010 QA-Staff-04-14-2010]<br />
** [[QA/StaffMeetings/QA-Staff-04-28-2010|QA-Staff-04-28-2010]]<br />
* Mar<br />
** [https://intranet.mozilla.org/QA-Staff-03-10-2010 QA-Staff-03-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-17-2010 QA-Staff-03-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-24-2010 QA-Staff-03-24-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-31-2010 QA-Staff-03-31-2010]<br />
* Feb<br />
** [https://intranet.mozilla.org/QA-Staff-02-03-2010 QA-Staff-02-03-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-10-2010 QA-Staff-02-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-17-2010 QA-Staff-02-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-24-2010 QA-Staff-02-24-2010]<br />
|}</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2015-02-18&diff=1056844QA/Team Meeting/QA Team Meeting-2015-02-182015-02-18T19:58:28Z<p>Ctalbert: Created page with "= Mozilla QA Meeting Feb 18 2015 = # Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA # # Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNI..."</p>
<hr />
<div>= Mozilla QA Meeting Feb 18 2015 =<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
<br />
== Actions From Last Week ==<br />
<br />
== Deadlines and Schedules ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
=== Other Notable Dates/Events (Read Only) ===<br />
*<br />
<br />
== Discussion & Updates for Team ==<br />
* <small>''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''</small><br />
<br />
== Lightning Talk ==<br />
* <small>''[[QA/Team_Meeting/Lightning Talk List|Lightning talk list]]''</small><br />
<br />
== Contributors ==<br />
=== New Contributor Spotlight ===<br />
These are new contributors, if you see them around, say hello<br />
*<br />
<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO (Read Only) ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=User:KaiRo/Filing_Crash_Bugs&diff=1054894User:KaiRo/Filing Crash Bugs2015-02-09T23:48:16Z<p>Ctalbert: /* Understanding the Bugzilla hierarchy */</p>
<hr />
<div>This is a '''DRAFT''' for an article that might go up on MozillaWiki or MDC, wherever it fits better.<br />
<br />
If you file a bug for a crash you have encountered or found via [https://crash-stats.mozilla.com/ crash stats], there are a few rules you can follow if you want developers to be as efficient as possible in actually debugging the problem and finding a fix. (If you are unfamiliar with how we use Bugzilla in general, there's a [https://gerv.makes.org/popcorn/1bn6 helpful video] to watch.)<br />
<br />
* For one thing, use the "Bugzilla - Report this bug in ..." links in a representative crash report on crash-stats (under the table of crash information on the "Details" tab). If you are looking at a list of crashes, e.g. a Signature Summary, you ideally look through a few reports to select a representative that has a good stack and as few extensions installed as possible.<br />
** The best way to detect if a stack is "good" is to look at a few ones. When you have some that have random hexadecimal addresses in them or that end after just a few lines (frames), those are somewhat "bad". If you have multiple crash reports available, try to find one where the stack does not contain such random address and is going down for a more than 10-15 frames, if possible. That helps developers find the whole trace of functions that have been called to get to the place that finally crashed.<br />
* Select a fitting product and component for what you think is the cause of the crash.<br />
** If you don't have good knowledge of our code and Bugzilla hierarchies, it can be helpful to look into bugs connected with recent changes to the files linked in the significant top frames of the stack. This takes a number of clicks, but clicking at those links at the right-side column of the stack and then clicking "revisions" at the top of the resulting page (on hg.mozilla.org) is quite helpful and links to bugs that changed this code recently. Using the product/components mostly mentioned in those bugs for recent entries is usually a good start.<br />
** Which frames are significant is something you need to use some personal judgement on. Look for frames that are not generic things like "abort", "alloc(ate)" or "processNextEvent" or similar, and try to guess based on what function names there sound like they would actually perform some crucial action and not to be generic intermediate steps.<br />
** The less experience you have, the more guessing all this will be, but don't fear, you won't get judged badly if you guess wrong, and doing that guessing is a learning experience and you'll be pretty proud of yourself once you manage to guess correctly a few times! Take an as educated as possible guess. The more often you do this, the better you will get.<br />
* Make sure a link to the representative crash is in the initial comment, the Crash Signature field filled out and the "crash" keyword set on the bug. If you used the "Report this bug" links, then this is already done correctly.<br />
* Include a link to more reports with the same signature, e.g. by copying the URL from the "More Reports" link next to the signature in the Details table of the crash report.<br />
* It helps including the top few stack frames in the bug - you can potentially cut the list off at a point where it seems to go generic and unrelated to the actual issue, but if you are not sure, include it all.<br />
** This is another step that involves some guessing. A good thumb rule is to not go much further than 10-15 frames, and often you have something generic like nsThread::ProcessNextEvent in there, which usually is a good point to cut off and add a "[...]" at the end. See for example what was done in {{bug|1074196}}.<br />
** "Generic" there is meant in what the code is doing. If it's part of an event loop, for example (stuff like "ProcessNextEvent" or so point to that), this is very generic. Also, functions that actually just handle the error but didn't produce it themselves, like "malloc_abort" are also pretty generic.<br />
* If it's a crash you encountered, it helps to tell developers in the bug what you remember doing when the crash occurred, if possible.<br />
* If you file based on data, please include data about when it started to appear, how high it is in overall volume (and/or topcrash reports), and any information that is outside the average sample (i.e. only happening on specific OSes, specific Firefox versions, specific Graphics cards, or significant correlations with any modules or add-ons). Also, if comments tell anything about commonalities of actions and/or possible steps to reproduce, please include that. See the walkthrough below for some tips on how to get that.<br />
* Include any clues you have about this crash could be reproduced. When a developer can reproduce the crash, it's very likely they can find a fix as well.<br />
* Examples of good crash bug reports: {{bug|1035168}}<br />
<br />
== Example walkthrough ==<br />
Let's take {{bug|1074196}} as an example again as I mentioned it before. As mentioned at the start of the initial comment, I filed it from this crash report: https://crash-stats.mozilla.com/report/index/fd16294d-0bbf-4530-b2d4-65c2d2140929. This specific crash report expires 6 months after it was submitted and some info is only shown for a shorter time, so you might not see exactly the same as I did.<br />
<br />
The lower section of the report has the crash stack with a header of "Crashing Thread". The right-hand column of this table has file names that are linked to actual code. For example clicking the first one there goes to line 228 of nsUrlClassifierPrefixSet.cpp, I click the "gpascutto@197683" link on the left next to the code line 228, which links to the actual code changes that a person with the (nick) name of gpascutto did in the changeset no. 197683 of our code. From there, I click again on the link "9d24ecc84a50" (that's a random identifier for this changeset) next to "changeset 197683". That makes me see the actual comment that gpascutto made for this changeset, in this case "Bug 1046038 - Replace linear prefix array by array of arrays. r=mmc". Finally, I can click on the bug linked there and look at their data, like product and component.<br />
<br />
This takes a lot of clicks unfortunately, and there's ideas on how to improve it (the cvs-based system we had before Mercurial/"hg" actually showed the comment and bug link right when you moved your mouse over the name of the person that changed the line in the first code view of this process) - but for now, this series of clicks is what is needed there.<br />
<br />
With those steps, I find that the product "Toolkit", component "Phishing Protection", so in the crash report, I clicked the "Toolkit" link next to "Report this bug in" within the Bugzilla section in about the middle of the page when scrolling down. Back on the crash report, I go to the top and click the "More Reports" link to get to a signature summary page to get more info about those crashes.<br />
<br />
Looking through those, I try to find properties that fall out of the ordinary (like only few Product versions being listed in the "Products" section, only very specific OSes listed, or specific graphics adapters, or much fewer installations than crashes listed in "Crashes per Install"), and looking at the list in the "Reports" tab, some things like the same address on all reports are interesting as well. All those should be listed in a comment on the bug report. Posting a link to the "More Reports" page is usually a very good idea as well.<br />
<br />
Explaining the full hierarchy is not really possible, and it changes all the time in terms of components being added, some also retired. But I can give you a few pointers to the cornerstones, so to speak. Note that all this has grown organically over the 15+ years that the Mozilla project and Bugzilla have exited now, so some things might not be the same as one would design from scratch.<br />
<br />
== Understanding the Bugzilla hierarchy ==<br />
<br />
The most important pieces:<br />
# There's Bugzilla "products" for, logically, the major products we have at Mozilla, like Firefox, Firefox for Android, Firefox OS, Thunderbird, SeaMonkey, etc. - those are *only* about things that are specific to that one product and not in code that multiple of those products share.<br />
# For shared code, there's the "Core" product, which has all the underpinnings of Gecko and "the Mozilla platform", like Grpahics, Javascript Engine, networking, etc. - and there's "Toolkit" for some other shared code that is closer to or including user interface pieces, like Add-ons Manager, and some other pieces. The difference between those parts is fluid and many of us often don't know what is in which of those two, you have to search and learn here.<br />
# There are a lot of supporting "products" like for websites and server software, legal issues, localizations, IT operations, 3rd-party plugins, etc. - you can ignore them most of the time, but sometimes you might get directed to one for something. Best is to not try to understand more of those than what you run across and need for a certain task.<br />
# All those "products" in Bugzilla have "components" underneath them. When filing a bug in Bugzilla, once you have selected a product, there's a description of the component displayed when you select one from the list. Try to use your best guess from those descriptions of where your bugs fits. It's easy to change afterwards and we put bugs into "wrong" components all the time as well as for some things it's just hard to figure out or lines are blurry. Don't shy away from setting one, it's easy to move to a different one afterwards if you guess wrong.<br />
<br />
The general rule here like with many other things in our community is: Guess and try to do what makes most sense for you, nobody will think less of you if you guess wrong. Be bold and try what sounds the best way for you and learn as you go. It's better to try and learn than not to try in the first place.</div>Ctalberthttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2015-02-09&diff=1054754WeeklyUpdates/2015-02-092015-02-09T17:51:15Z<p>Ctalbert: /* Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} */</p>
<hr />
<div><br />
{{WeeklyUpdateNav}}<br />
{{conf|8600}}<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
* The biggest IT Expo of Bangladesh [https://reps.mozilla.org/e/mozilla-booth-basis-digital-world-2015/ Digital World Bangladesh] is happening from 9th to 12nd February. Local Community of Bangladesh is perticipating there with two booths representing Mozilla.<br />
** Largest Software Expo of Bangladesh<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
* Quality and Automation community Call tomorrow. Come discuss projects you're working on and areas where you can get involved: https://etherpad.mozilla.org/Quality-Automation-Call-2015-02-10<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
* Watch mconley livehack on Firefox Desktop bugs on Air Mozilla! [https://air.mozilla.org/the-joy-of-coding-mconley-livehacks-on-firefox-episode-1/ The first episode of "The Joy of Coding" starts at 1PM Eastern time]. Using #livehacking on irc.mozilla.org as a backchannel. [http://mikeconley.ca/blog/2015/02/08/the-joy-of-coding-or-firefox-hacking-live/ See this blog post for additional details.]<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br />
<br />
=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
The [[WebCompat Summit (2015)|WebCompat Summit]] is happening on Wednesday February 18th at the Mountain View office. Ping miket@mozilla.com if you would like to participate!<br />
<br />
== Project Status Updates (voice updates) ==<br />
<br />
=== Firefox ===<br />
''Speaker Location:''<br />
<br />
=== Firefox OS ===<br />
''Speaker Location:''<br />
<br />
=== Cloud Services ===<br />
''Speaker Location:''<br />
<br />
=== CTO Update ===<br />
''Speaker Location:''<br />
<br />
=== Content Services ===<br />
''Speaker Location:''<br />
<br />
=== Webmaker ===<br />
''Speaker Location:''<br />
<br />
=== Mozilla Communities ===<br />
''Speaker Location:''<br />
<br />
== Speakers ==<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! [https://mozillians.org/u/USERNAME Presenter]<br />
! Title<br />
! Topic<br />
! Location<br />
! Share?<br />
! Media<br />
! More Details<br />
|-<br />
| Who Are You?<br />
| What Do You Do?<br />
| What are you going to talk about?<br />
| Where are you presenting from? (Moz Space, your house, space)<br />
| Will you be sharing your screen? (yes/no, other info)<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Dave Steer<br />
| Advocacy<br />
| Mozilla's Net Neutrality Campaign<br />
| SF<br />
| Yes<br />
|<br />
|<br />
|-<br />
| Liz Compton<br />
| Legal Team<br />
| Introduce the Data Compliance Team<br />
| San Francisco<br />
| No<br />
|<br />
| https://mana.mozilla.org/wiki/display/LGL/Legal+Resources+Home<br />
|}<br />
<br />
= Roundtable =<br />
<br />
Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.<br />
<br />
Please note that we may not always be able to get to every item on this list, but we will try!<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Who are you?<br />
! Area of question<br />
! Question<br />
|-<br />
| ''What's your name? What do you work on?''<br />
| ''Is your question about policy, a product, a Foundation initiative, etc.''<br />
| ''What would you like to know?''<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
= Welcome! =<br />
<br />
Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br />
<br />
== Introducing New Volunteers ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Volunteer(s)<br />
! Introduced by<br />
! Speaker location<br />
! New Volunteer location<br />
! Will be working on<br />
|-<br />
| ''Who is the new volunteer(s)?''<br />
| ''Who will be introducing that person?''<br />
| ''Where is the introducer?''<br />
| ''Where is the new person based?''<br />
| ''What will the new person be doing?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
== Introducing New Hires ==<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! New Hire<br />
! Introduced by<br />
! Speaker location<br />
! New Hire location<br />
! Will be working on<br />
|-<br />
| ''Who is the new hire?''<br />
| ''Who will be introducing that person?''<br />
| ''Where is the introducer?''<br />
| ''Where will the new person be working from?''<br />
| ''What will the new person be working on?''<br />
|-<br />
| Samael Wang<br />
| Bevis Tseng<br />
| (Recorded)<br />
| Taipei, Taiwan<br />
| Software Engineering<br />
|-<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
== Introducing New Interns ==<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! New Intern<br />
! Introduced by<br />
! Speaker location<br />
! New Hire location<br />
! Will be working on<br />
|-<br />
| ''Who is the new intern?''<br />
| ''Who will be introducing that person?''<br />
| ''Where is the introducer?''<br />
| ''Where will the new person be working from?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
= &lt;meta&gt; =<br />
<br />
Notes and non-voice status updates that aren't part of the live meeting go here.<br />
<br />
== Status Updates By Team (*non-voice* updates) ==<br />
<br />
=== Firefox ===<br />
<br />
=== Platform ===<br />
<br />
=== Cloud Services ===<br />
<br />
=== Messaging ===<br />
<br />
=== Mobile ===<br />
<br />
=== IT ===<br />
<br />
=== Release Engineering ===<br />
<br />
=== QA ===<br />
<br />
==== Test Execution ====<br />
<br />
==== WebQA ====<br />
<br />
==== QA Community ====<br />
<br />
=== Automation & Tools ===<br />
Notable changes to [https://bugzilla.mozilla.org/ bugzilla.mozilla.org] during the last week:<br />
* {{bug|1045145}} Users can now issue API Keys, and use them to authenticate with Bugzilla's API. This provides revokable password-less authenticate.<br />
[[BMO/Recent_Changes|All changes]].<br />
<br />
=== Security ===<br />
<br />
=== Engagement ===<br />
<br />
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]<br />
<br />
==== PR ====<br />
<br />
==== Events ====<br />
<br />
==== Social Support ====<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2015-02-04&diff=1053710QA/Team Meeting/QA Team Meeting-2015-02-042015-02-04T19:34:43Z<p>Ctalbert: /* Discussion & Updates for Team */</p>
<hr />
<div>= Mozilla QA Meeting Feb 4 2015 =<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
<br />
== Actions From Last Week ==<br />
<br />
== Deadlines and Schedules ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
=== Other Notable Dates/Events (Read Only) ===<br />
*<br />
<br />
== Discussion & Updates for Team ==<br />
* <small>''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''</small><br />
* Note the new format, review the list of lightningtalks<br />
* Review Goals quickly<br />
* Review the release trains<br />
* Review the Firefox 38 plan<br />
<br />
== Lightning Talk ==<br />
* <small>''[[QA/Team_Meeting/Lightning Talk List|Lightning talk list]]''</small><br />
<br />
== Contributors ==<br />
=== New Contributor Spotlight ===<br />
These are new contributors, if you see them around, say hello<br />
*<br />
<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO (Read Only) ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
http://i.imgur.com/Bt3qlPZ.gif</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Platform/DOM&diff=1051478QA/Platform/DOM2015-01-29T21:56:26Z<p>Ctalbert: /* Sprint 3 */</p>
<hr />
<div>= Summary =<br />
This page documents the strategy for testing and ensuring the quality of Gecko's DOM code.<br />
<br />
; QA Contacts<br />
* [mailto:ahughes@mozilla.com Anthony Hughes] (IRC: ashughes)<br />
* [mailto:twalker@mozilla.com Tracy Walker] (IRC: tracy)<br />
<br />
= Goal =<br />
Support DOM efforts to bring firefox back to the forefront of developer mindshare through exposing more of the web platform to community and ensuring the quality of the new features being implemented for the web platform.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Bug triage and documentation to further contributor involvement<br />
# Define and establish base-line quality metrics for DOM<br />
# [https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html Service Workers] spec coverage in web platform tests<br />
# [http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#the-picture-element Picture Tag] spec coverage in web platform tests<br />
<br />
= To Do =<br />
1) Establishing a Baseline<br />
* Define "high quality" for this project and its stakeholders, and establish metrics<br />
* Define how are bugs logged and triaged, establish metrics on bug flow<br />
* Review and document existing automated/manual test coverage<br />
* Document dependencies this code has on other components<br />
* Document prefs for enabling/disabling features, default values and their effect<br />
* Document special hardware, software, and/or skills required to contribute<br />
* Narrow down "DOM" into a set of scoped things so we can prioritize and strategize the scopeable things<br />
<br />
2) Developing a Strategy<br />
* Identify the features and their primary use cases<br />
* Define minimum acceptance and develop smoketests to ensure that's covered<br />
* Define end-to-end tests and how those should be implemented<br />
* Define areas community can contribute, establish metrics to measure community success<br />
* Define bug triage process including how bugs are prioritized<br />
* Define the criteria for what qualifies a bug as needing QE verification<br />
* Define best practices and begin on-boarding community members to support them<br />
<br />
3) Develop an execution plan<br />
* Divide the strategy into work that can be accomplished within two weeks<br />
* Document a roadmap of what's being worked on, what's next on the list, and what's down the road<br />
* Determine how success of each sprint will be measured and make adjustments based on these measurements<br />
* Review accomplishments and setbacks at the end of each sprint<br />
<br />
4) Establish Milestones<br />
* Code not riding the trains: verify merged branches do *not* have the code and that nothing has regressed<br />
* Code riding the trains: verify automation, manual test coverage, metrics in place to qualify<br />
* Define go-no-go requirements for each branch milestone<br />
* Define any ''all hands'' testing requirements for the Beta phase<br />
<br />
= Template =<br />
; ''To be edited as necessary''<br />
<br />
== Introduction ==<br />
; ''Brief description of the area/feature(s) covered by this document.''<br />
The primary purpose here is provide enough information about this functional area to a new person that they will be able to achieve a basic understanding of the feature and provide links to the any documentation or engineering docs for further reading is needed. If this is a new feature include which release it is targeted at.<br />
<br />
== Testing Approach ==<br />
; ''High level overview of the testing methodologies used in each type of testing done for this project (Manual and Automated)''<br />
<br />
The purpose of this section is provide guidance on how this area can be tested and what methodologies are most likely to be productive. For example when testing WebRTC the approach for manual testing would be to initiate calls connections between to clients and verify audio and video quality. The automated approach would be to use predictable data sources for audio and video steams allowing you to preform data analysis on the call statistics. Additionally you will want to provide some guidance on what can and can not be tested. <br />
<br />
Include:<br />
* Examples of things to watch for. <br />
* What are some of common errors and issues that this testing is targeted at finding <br />
* Filing Bugs <br />
** How are bugs reported. <br />
** What component(s) should they be filed under <br />
** Define keywords, whiteboard tags and other flags or verbage that is expected to be used when reporting bugs <br />
<br />
== Get Involved ==<br />
; ''How can volunteers and community members become involved in this project.''<br />
* Links to One and Done tasks <br />
* Links to Moztrap tests<br />
* Good First Verify in bugzilla <br />
* Links to any tutorials and other QA introductory material <br />
* Contact information and Meetings schedules and information on how to join <br />
<br />
== Requirements ==<br />
; ''What are the minimum requirements for becoming involved (Hardware, Software, Skills)''<br />
* Describe the required test environment and provide instructions on how to create it. <br />
* If special skills are required, provide links to any tutorials that may be available on the subject.<br />
* If special hardware is required, provide steps on how to verify that the testers systems meet the minimum requirements.<br />
<br />
== Related Prefs ==<br />
; ''Define any preferences or about:config options that are related to the behavior of this area''<br />
Describe what pref or option does and what values should be used and how they will change the behavior of the browser. Be sure to include what the default value should be.<br />
<br />
== Related Features ==<br />
; ''What other features are either directly related too or can be affected by changes made to this feature.'' <br />
<br />
For instance, changes to the javascript engine can have effects on emscipten and asm.js. WebRTC has dependencies on graphics (Open H.264) and Networking. <br />
<br />
== Test Cases ==<br />
; ''Define the test cases required to test this feature/area.''<br />
Include which tests can and should be automated, which framework used and how often the should be executed. * Provide link to repository(ies) for automated tests. <br />
* Smoke<br />
* Describe basic smoke tests required to prove minimum acceptance <br />
* Functional <br />
* List each major functional area to be tested and basic concepts for testing <br />
* End-to-end User Stories <br />
* Describe primary use cases <br />
* Exploratory<br />
* Describe some related areas and user stories that may be useful to explore <br />
<br />
== Bug Triage ==<br />
; ''Methodology for bug triage''<br />
* Criteria for determining priority '''(discussion item)''' <br />
* Minimum criteria for internal verification (qe-verify+) '''(discussion item)'''<br />
* Setup regular triage session(s)<br />
<br />
; Queries (in order of priority)<br />
* verification: from above discussion item<br />
* [http://mzl.la/1BFmneX unconfirmed all]: see if there's any bugs that need reproducing or need clearer STR's<br />
* [http://mzl.la/1wSHQgk unconfirmed general]: move bugs into the appropriate sub-component<br />
* intermittent failures: developers feel this is the least useful task we can be doing. But if time and interest allows, they suggest:<br />
** 1. Getting an idea on how reproducible the issue is. For example, can you reproduce the failure in 20 test runs locally? Can you reproduce on the try server? What if you got a loan on a slave and ran tests on the slave? If the failure happens on Linux, and you have a machine that engineers can log into remotely, capturing an rr <http://rr-project.org/> trace of the failure would be tremendously helpful.<br />
** 2. When did it start to happen? Did it happen for as long the test was added or did it start to happen way after the test was originally written? Can you go back on TBPL and retrigger test runs there to try to narrow down when the failure started to happen? (Being able to reproduce locally obviously helps with bisection as well.)<br />
<br />
== Risks ==<br />
; ''What are the primary areas of risk involved in this area.'' <br />
For example Graphics has the risk of not being to have a broad enough test bed to provide coverage for edge case testing and may result in unexpected behavior when released to a wider audience. <br />
<br />
== Reporting and Status ==<br />
; ''Describe how are test results reported and provide links to any automated test reports or dashboards.''<br />
* List milestones and current progress <br />
* Include bug queries for tracked bugs <br />
* Sign-off status for each release tested.<br />
<br />
= Ramp Up =<br />
; People<br />
* Lead: Andrew Overholt<br />
* Mentors: Ehsan Akhgari, Anne van Kesteren, Josh Matthews, Boris Zbarsky<br />
<br />
; [https://wiki.mozilla.org/Platform/Roadmap#DOM 2015 Roadmap]<br />
* [https://github.com/w3c/web-platform-tests Web Platform Tests]<br />
** Automated cross-browser testing of features that involve UI (e.g. permission UI)<br />
* Web Components<br />
* Service Workers<br />
* Making bugs actionable<br />
** Communicating with the bug reporter to ask them about the specifics of their report<br />
** Attempting to reproduce the bugs, perhaps by writing test cases<br />
** Gaining an understanding of who works on what in DOM, to be able to get the right eyes on bugs<br />
** Providing regression ranges and ideally identifying the commit that regressed something<br />
** Using various debugging tools (such as the built-in devtools, gdb, address sanitizer, rr, etc.) to gain more information on bugs<br />
* 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<br />
<br />
; Documentation<br />
* [https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model MDN]<br />
* How to build Nightly (Developer build of Firefox)<br />
** If you don't have mercurial installed, follow instructions to do so here: https://developer.mozilla.org/en-US/docs/Installing_Mercurial<br />
** 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<br />
* How to setup git.<br />
** get and install git from: http://www.git-scm.com/downloads<br />
*** (optional) You may also want to use a git GUI. Here's a popular version: GitHub from http://www.git-scm.com/downloads/guis.<br />
* Get the web-platform-tests and run them from the browser<br />
** With git is installed, in a terminal, run "git clone https://github.com/w3c/web-platform-tests.git"<br />
** Complete instructions for running the tests from the browser are here: https://github.com/w3c/web-platform-tests/blob/master/README.md<br />
* Run the web-platform-tests of the Nightly build.<br />
** Instructions are here: https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/README.md<br />
** For example, to run the dom javascript tests:<br />
*** 1. <hg pull and update your mozilla-central - steps here depend on how you set up your mozilla-central directory><br />
*** 2. cd <mozilla-central><br />
*** 3. ./mach build (./mach clobber may be required)<br />
*** 4. ./mach web-platform-tests --test-type=testharness --include=dom<br />
* How to bisect<br />
** 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.<br />
* [https://wiki.mozilla.org/WebAPI wiki]<br />
<br />
; Mailing Lists<br />
* mozilla.dev.platform<br />
* mozilla.dev.webapi<br />
<br />
= Meetings =<br />
== Kickoff ==<br />
Good starting points: [https://etherpad.mozilla.org/qa-dom-strategy etherpad]<br />
* tracking down regression ranges for intermittents (Ehsan will need info us on some bugs)<br />
* web platform tests: [http://testthewebforward.org/docs/ docs], [https://github.com/w3c/web-platform-tests/ repo] - start with reaching out to ms2ger/jgraham to find a good-first-issue to work on (DOM, HTML)<br />
* incoming triage<br />
** interesting to see what the volume of bug work is per sub-component<br />
** moving bugs from DOM:Core General to something more appropriate<br />
** consult bz's [https://etherpad.mozilla.org/WhatToDoWithIncomingDOMBugs etherpad]<br />
* community<br />
** work with ms2ger to find ways we can involve community<br />
<br />
Not discussed:<br />
* outgoing triage<br />
* features<br />
<br />
Next Steps:<br />
* Anthony to email team about outgoing triage (testing fixes or making sure fixes have sufficient coverage), features (what we need to be paying attention to), and incoming bug triage (All of DOM -1m to start then 24hr going forward, if load becomes too big we'll prioritize subcomponents and seek to involve community to pick up the slack)<br />
* Ehsan to needinfo us on regression window wanted bugs<br />
* Tracy & Anthony select some work from web platform tests<br />
* Tracy & Anthony to figure out goals and document (review *this* document as well)<br />
* Set up a triage meeting for the DOM team to go through to teach us what to do for different bugs<br />
<br />
= Sprint 3=<br />
* Anthony to mock up something with unconfirmed bugs<br />
* Get DOM team (Andrew and whoever else) to review benchmarks and metrics from bugzilla<br />
* If benchmarks pass muster Anthony to look at automating them/metrics.js etc<br />
* Tracy to set up bug triage<br />
* Tracy to document the bug workflow w.r.t. verification - when do we verify a bug<br />
* Anthony and Tracy - review the big todo list above and understand what is required for us and what is not, cross out things that are done and eliminate things that we're not doing<br />
* Look into what "developer preview" actually means w.r.t. service workers.</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Platform/DOM&diff=1051477QA/Platform/DOM2015-01-29T21:47:13Z<p>Ctalbert: /* Sprint 3 */</p>
<hr />
<div>= Summary =<br />
This page documents the strategy for testing and ensuring the quality of Gecko's DOM code.<br />
<br />
; QA Contacts<br />
* [mailto:ahughes@mozilla.com Anthony Hughes] (IRC: ashughes)<br />
* [mailto:twalker@mozilla.com Tracy Walker] (IRC: tracy)<br />
<br />
= Goal =<br />
Support DOM efforts to bring firefox back to the forefront of developer mindshare through exposing more of the web platform to community and ensuring the quality of the new features being implemented for the web platform.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Bug triage and documentation to further contributor involvement<br />
# Define and establish base-line quality metrics for DOM<br />
# [https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html Service Workers] spec coverage in web platform tests<br />
# [http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#the-picture-element Picture Tag] spec coverage in web platform tests<br />
<br />
= To Do =<br />
1) Establishing a Baseline<br />
* Define "high quality" for this project and its stakeholders, and establish metrics<br />
* Define how are bugs logged and triaged, establish metrics on bug flow<br />
* Review and document existing automated/manual test coverage<br />
* Document dependencies this code has on other components<br />
* Document prefs for enabling/disabling features, default values and their effect<br />
* Document special hardware, software, and/or skills required to contribute<br />
* Narrow down "DOM" into a set of scoped things so we can prioritize and strategize the scopeable things<br />
<br />
2) Developing a Strategy<br />
* Identify the features and their primary use cases<br />
* Define minimum acceptance and develop smoketests to ensure that's covered<br />
* Define end-to-end tests and how those should be implemented<br />
* Define areas community can contribute, establish metrics to measure community success<br />
* Define bug triage process including how bugs are prioritized<br />
* Define the criteria for what qualifies a bug as needing QE verification<br />
* Define best practices and begin on-boarding community members to support them<br />
<br />
3) Develop an execution plan<br />
* Divide the strategy into work that can be accomplished within two weeks<br />
* Document a roadmap of what's being worked on, what's next on the list, and what's down the road<br />
* Determine how success of each sprint will be measured and make adjustments based on these measurements<br />
* Review accomplishments and setbacks at the end of each sprint<br />
<br />
4) Establish Milestones<br />
* Code not riding the trains: verify merged branches do *not* have the code and that nothing has regressed<br />
* Code riding the trains: verify automation, manual test coverage, metrics in place to qualify<br />
* Define go-no-go requirements for each branch milestone<br />
* Define any ''all hands'' testing requirements for the Beta phase<br />
<br />
= Template =<br />
; ''To be edited as necessary''<br />
<br />
== Introduction ==<br />
; ''Brief description of the area/feature(s) covered by this document.''<br />
The primary purpose here is provide enough information about this functional area to a new person that they will be able to achieve a basic understanding of the feature and provide links to the any documentation or engineering docs for further reading is needed. If this is a new feature include which release it is targeted at.<br />
<br />
== Testing Approach ==<br />
; ''High level overview of the testing methodologies used in each type of testing done for this project (Manual and Automated)''<br />
<br />
The purpose of this section is provide guidance on how this area can be tested and what methodologies are most likely to be productive. For example when testing WebRTC the approach for manual testing would be to initiate calls connections between to clients and verify audio and video quality. The automated approach would be to use predictable data sources for audio and video steams allowing you to preform data analysis on the call statistics. Additionally you will want to provide some guidance on what can and can not be tested. <br />
<br />
Include:<br />
* Examples of things to watch for. <br />
* What are some of common errors and issues that this testing is targeted at finding <br />
* Filing Bugs <br />
** How are bugs reported. <br />
** What component(s) should they be filed under <br />
** Define keywords, whiteboard tags and other flags or verbage that is expected to be used when reporting bugs <br />
<br />
== Get Involved ==<br />
; ''How can volunteers and community members become involved in this project.''<br />
* Links to One and Done tasks <br />
* Links to Moztrap tests<br />
* Good First Verify in bugzilla <br />
* Links to any tutorials and other QA introductory material <br />
* Contact information and Meetings schedules and information on how to join <br />
<br />
== Requirements ==<br />
; ''What are the minimum requirements for becoming involved (Hardware, Software, Skills)''<br />
* Describe the required test environment and provide instructions on how to create it. <br />
* If special skills are required, provide links to any tutorials that may be available on the subject.<br />
* If special hardware is required, provide steps on how to verify that the testers systems meet the minimum requirements.<br />
<br />
== Related Prefs ==<br />
; ''Define any preferences or about:config options that are related to the behavior of this area''<br />
Describe what pref or option does and what values should be used and how they will change the behavior of the browser. Be sure to include what the default value should be.<br />
<br />
== Related Features ==<br />
; ''What other features are either directly related too or can be affected by changes made to this feature.'' <br />
<br />
For instance, changes to the javascript engine can have effects on emscipten and asm.js. WebRTC has dependencies on graphics (Open H.264) and Networking. <br />
<br />
== Test Cases ==<br />
; ''Define the test cases required to test this feature/area.''<br />
Include which tests can and should be automated, which framework used and how often the should be executed. * Provide link to repository(ies) for automated tests. <br />
* Smoke<br />
* Describe basic smoke tests required to prove minimum acceptance <br />
* Functional <br />
* List each major functional area to be tested and basic concepts for testing <br />
* End-to-end User Stories <br />
* Describe primary use cases <br />
* Exploratory<br />
* Describe some related areas and user stories that may be useful to explore <br />
<br />
== Bug Triage ==<br />
; ''Methodology for bug triage''<br />
* Criteria for determining priority '''(discussion item)''' <br />
* Minimum criteria for internal verification (qe-verify+) '''(discussion item)'''<br />
* Setup regular triage session(s)<br />
<br />
; Queries (in order of priority)<br />
* verification: from above discussion item<br />
* [http://mzl.la/1BFmneX unconfirmed all]: see if there's any bugs that need reproducing or need clearer STR's<br />
* [http://mzl.la/1wSHQgk unconfirmed general]: move bugs into the appropriate sub-component<br />
* intermittent failures: developers feel this is the least useful task we can be doing. But if time and interest allows, they suggest:<br />
** 1. Getting an idea on how reproducible the issue is. For example, can you reproduce the failure in 20 test runs locally? Can you reproduce on the try server? What if you got a loan on a slave and ran tests on the slave? If the failure happens on Linux, and you have a machine that engineers can log into remotely, capturing an rr <http://rr-project.org/> trace of the failure would be tremendously helpful.<br />
** 2. When did it start to happen? Did it happen for as long the test was added or did it start to happen way after the test was originally written? Can you go back on TBPL and retrigger test runs there to try to narrow down when the failure started to happen? (Being able to reproduce locally obviously helps with bisection as well.)<br />
<br />
== Risks ==<br />
; ''What are the primary areas of risk involved in this area.'' <br />
For example Graphics has the risk of not being to have a broad enough test bed to provide coverage for edge case testing and may result in unexpected behavior when released to a wider audience. <br />
<br />
== Reporting and Status ==<br />
; ''Describe how are test results reported and provide links to any automated test reports or dashboards.''<br />
* List milestones and current progress <br />
* Include bug queries for tracked bugs <br />
* Sign-off status for each release tested.<br />
<br />
= Ramp Up =<br />
; People<br />
* Lead: Andrew Overholt<br />
* Mentors: Ehsan Akhgari, Anne van Kesteren, Josh Matthews, Boris Zbarsky<br />
<br />
; [https://wiki.mozilla.org/Platform/Roadmap#DOM 2015 Roadmap]<br />
* [https://github.com/w3c/web-platform-tests Web Platform Tests]<br />
** Automated cross-browser testing of features that involve UI (e.g. permission UI)<br />
* Web Components<br />
* Service Workers<br />
* Making bugs actionable<br />
** Communicating with the bug reporter to ask them about the specifics of their report<br />
** Attempting to reproduce the bugs, perhaps by writing test cases<br />
** Gaining an understanding of who works on what in DOM, to be able to get the right eyes on bugs<br />
** Providing regression ranges and ideally identifying the commit that regressed something<br />
** Using various debugging tools (such as the built-in devtools, gdb, address sanitizer, rr, etc.) to gain more information on bugs<br />
* 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<br />
<br />
; Documentation<br />
* [https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model MDN]<br />
* How to build Nightly (Developer build of Firefox)<br />
** If you don't have mercurial installed, follow instructions to do so here: https://developer.mozilla.org/en-US/docs/Installing_Mercurial<br />
** 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<br />
* How to setup git.<br />
** get and install git from: http://www.git-scm.com/downloads<br />
*** (optional) You may also want to use a git GUI. Here's a popular version: GitHub from http://www.git-scm.com/downloads/guis.<br />
* Get the web-platform-tests and run them from the browser<br />
** With git is installed, in a terminal, run "git clone https://github.com/w3c/web-platform-tests.git"<br />
** Complete instructions for running the tests from the browser are here: https://github.com/w3c/web-platform-tests/blob/master/README.md<br />
* Run the web-platform-tests of the Nightly build.<br />
** Instructions are here: https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/README.md<br />
** For example, to run the dom javascript tests:<br />
*** 1. <hg pull and update your mozilla-central - steps here depend on how you set up your mozilla-central directory><br />
*** 2. cd <mozilla-central><br />
*** 3. ./mach build (./mach clobber may be required)<br />
*** 4. ./mach web-platform-tests --test-type=testharness --include=dom<br />
* How to bisect<br />
** 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.<br />
* [https://wiki.mozilla.org/WebAPI wiki]<br />
<br />
; Mailing Lists<br />
* mozilla.dev.platform<br />
* mozilla.dev.webapi<br />
<br />
= Meetings =<br />
== Kickoff ==<br />
Good starting points: [https://etherpad.mozilla.org/qa-dom-strategy etherpad]<br />
* tracking down regression ranges for intermittents (Ehsan will need info us on some bugs)<br />
* web platform tests: [http://testthewebforward.org/docs/ docs], [https://github.com/w3c/web-platform-tests/ repo] - start with reaching out to ms2ger/jgraham to find a good-first-issue to work on (DOM, HTML)<br />
* incoming triage<br />
** interesting to see what the volume of bug work is per sub-component<br />
** moving bugs from DOM:Core General to something more appropriate<br />
** consult bz's [https://etherpad.mozilla.org/WhatToDoWithIncomingDOMBugs etherpad]<br />
* community<br />
** work with ms2ger to find ways we can involve community<br />
<br />
Not discussed:<br />
* outgoing triage<br />
* features<br />
<br />
Next Steps:<br />
* Anthony to email team about outgoing triage (testing fixes or making sure fixes have sufficient coverage), features (what we need to be paying attention to), and incoming bug triage (All of DOM -1m to start then 24hr going forward, if load becomes too big we'll prioritize subcomponents and seek to involve community to pick up the slack)<br />
* Ehsan to needinfo us on regression window wanted bugs<br />
* Tracy & Anthony select some work from web platform tests<br />
* Tracy & Anthony to figure out goals and document (review *this* document as well)<br />
* Set up a triage meeting for the DOM team to go through to teach us what to do for different bugs<br />
<br />
= Sprint 3=<br />
* Anthony to mock up something with unconfirmed bugs<br />
* Get DOM team (Andrew and whoever else) to review benchmarks and metrics from bugzilla<br />
* If benchmarks pass muster Anthony to look at automating them/metrics.js etc<br />
* Tracy to set up bug triage<br />
* Tracy to document the bug workflow w.r.t. verification - when do we verify a bug</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Platform/DOM&diff=1051475QA/Platform/DOM2015-01-29T21:45:05Z<p>Ctalbert: </p>
<hr />
<div>= Summary =<br />
This page documents the strategy for testing and ensuring the quality of Gecko's DOM code.<br />
<br />
; QA Contacts<br />
* [mailto:ahughes@mozilla.com Anthony Hughes] (IRC: ashughes)<br />
* [mailto:twalker@mozilla.com Tracy Walker] (IRC: tracy)<br />
<br />
= Goal =<br />
Support DOM efforts to bring firefox back to the forefront of developer mindshare through exposing more of the web platform to community and ensuring the quality of the new features being implemented for the web platform.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Bug triage and documentation to further contributor involvement<br />
# Define and establish base-line quality metrics for DOM<br />
# [https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html Service Workers] spec coverage in web platform tests<br />
# [http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#the-picture-element Picture Tag] spec coverage in web platform tests<br />
<br />
= To Do =<br />
1) Establishing a Baseline<br />
* Define "high quality" for this project and its stakeholders, and establish metrics<br />
* Define how are bugs logged and triaged, establish metrics on bug flow<br />
* Review and document existing automated/manual test coverage<br />
* Document dependencies this code has on other components<br />
* Document prefs for enabling/disabling features, default values and their effect<br />
* Document special hardware, software, and/or skills required to contribute<br />
* Narrow down "DOM" into a set of scoped things so we can prioritize and strategize the scopeable things<br />
<br />
2) Developing a Strategy<br />
* Identify the features and their primary use cases<br />
* Define minimum acceptance and develop smoketests to ensure that's covered<br />
* Define end-to-end tests and how those should be implemented<br />
* Define areas community can contribute, establish metrics to measure community success<br />
* Define bug triage process including how bugs are prioritized<br />
* Define the criteria for what qualifies a bug as needing QE verification<br />
* Define best practices and begin on-boarding community members to support them<br />
<br />
3) Develop an execution plan<br />
* Divide the strategy into work that can be accomplished within two weeks<br />
* Document a roadmap of what's being worked on, what's next on the list, and what's down the road<br />
* Determine how success of each sprint will be measured and make adjustments based on these measurements<br />
* Review accomplishments and setbacks at the end of each sprint<br />
<br />
4) Establish Milestones<br />
* Code not riding the trains: verify merged branches do *not* have the code and that nothing has regressed<br />
* Code riding the trains: verify automation, manual test coverage, metrics in place to qualify<br />
* Define go-no-go requirements for each branch milestone<br />
* Define any ''all hands'' testing requirements for the Beta phase<br />
<br />
= Template =<br />
; ''To be edited as necessary''<br />
<br />
== Introduction ==<br />
; ''Brief description of the area/feature(s) covered by this document.''<br />
The primary purpose here is provide enough information about this functional area to a new person that they will be able to achieve a basic understanding of the feature and provide links to the any documentation or engineering docs for further reading is needed. If this is a new feature include which release it is targeted at.<br />
<br />
== Testing Approach ==<br />
; ''High level overview of the testing methodologies used in each type of testing done for this project (Manual and Automated)''<br />
<br />
The purpose of this section is provide guidance on how this area can be tested and what methodologies are most likely to be productive. For example when testing WebRTC the approach for manual testing would be to initiate calls connections between to clients and verify audio and video quality. The automated approach would be to use predictable data sources for audio and video steams allowing you to preform data analysis on the call statistics. Additionally you will want to provide some guidance on what can and can not be tested. <br />
<br />
Include:<br />
* Examples of things to watch for. <br />
* What are some of common errors and issues that this testing is targeted at finding <br />
* Filing Bugs <br />
** How are bugs reported. <br />
** What component(s) should they be filed under <br />
** Define keywords, whiteboard tags and other flags or verbage that is expected to be used when reporting bugs <br />
<br />
== Get Involved ==<br />
; ''How can volunteers and community members become involved in this project.''<br />
* Links to One and Done tasks <br />
* Links to Moztrap tests<br />
* Good First Verify in bugzilla <br />
* Links to any tutorials and other QA introductory material <br />
* Contact information and Meetings schedules and information on how to join <br />
<br />
== Requirements ==<br />
; ''What are the minimum requirements for becoming involved (Hardware, Software, Skills)''<br />
* Describe the required test environment and provide instructions on how to create it. <br />
* If special skills are required, provide links to any tutorials that may be available on the subject.<br />
* If special hardware is required, provide steps on how to verify that the testers systems meet the minimum requirements.<br />
<br />
== Related Prefs ==<br />
; ''Define any preferences or about:config options that are related to the behavior of this area''<br />
Describe what pref or option does and what values should be used and how they will change the behavior of the browser. Be sure to include what the default value should be.<br />
<br />
== Related Features ==<br />
; ''What other features are either directly related too or can be affected by changes made to this feature.'' <br />
<br />
For instance, changes to the javascript engine can have effects on emscipten and asm.js. WebRTC has dependencies on graphics (Open H.264) and Networking. <br />
<br />
== Test Cases ==<br />
; ''Define the test cases required to test this feature/area.''<br />
Include which tests can and should be automated, which framework used and how often the should be executed. * Provide link to repository(ies) for automated tests. <br />
* Smoke<br />
* Describe basic smoke tests required to prove minimum acceptance <br />
* Functional <br />
* List each major functional area to be tested and basic concepts for testing <br />
* End-to-end User Stories <br />
* Describe primary use cases <br />
* Exploratory<br />
* Describe some related areas and user stories that may be useful to explore <br />
<br />
== Bug Triage ==<br />
; ''Methodology for bug triage''<br />
* Criteria for determining priority '''(discussion item)''' <br />
* Minimum criteria for internal verification (qe-verify+) '''(discussion item)'''<br />
* Setup regular triage session(s)<br />
<br />
; Queries (in order of priority)<br />
* verification: from above discussion item<br />
* [http://mzl.la/1BFmneX unconfirmed all]: see if there's any bugs that need reproducing or need clearer STR's<br />
* [http://mzl.la/1wSHQgk unconfirmed general]: move bugs into the appropriate sub-component<br />
* intermittent failures: developers feel this is the least useful task we can be doing. But if time and interest allows, they suggest:<br />
** 1. Getting an idea on how reproducible the issue is. For example, can you reproduce the failure in 20 test runs locally? Can you reproduce on the try server? What if you got a loan on a slave and ran tests on the slave? If the failure happens on Linux, and you have a machine that engineers can log into remotely, capturing an rr <http://rr-project.org/> trace of the failure would be tremendously helpful.<br />
** 2. When did it start to happen? Did it happen for as long the test was added or did it start to happen way after the test was originally written? Can you go back on TBPL and retrigger test runs there to try to narrow down when the failure started to happen? (Being able to reproduce locally obviously helps with bisection as well.)<br />
<br />
== Risks ==<br />
; ''What are the primary areas of risk involved in this area.'' <br />
For example Graphics has the risk of not being to have a broad enough test bed to provide coverage for edge case testing and may result in unexpected behavior when released to a wider audience. <br />
<br />
== Reporting and Status ==<br />
; ''Describe how are test results reported and provide links to any automated test reports or dashboards.''<br />
* List milestones and current progress <br />
* Include bug queries for tracked bugs <br />
* Sign-off status for each release tested.<br />
<br />
= Ramp Up =<br />
; People<br />
* Lead: Andrew Overholt<br />
* Mentors: Ehsan Akhgari, Anne van Kesteren, Josh Matthews, Boris Zbarsky<br />
<br />
; [https://wiki.mozilla.org/Platform/Roadmap#DOM 2015 Roadmap]<br />
* [https://github.com/w3c/web-platform-tests Web Platform Tests]<br />
** Automated cross-browser testing of features that involve UI (e.g. permission UI)<br />
* Web Components<br />
* Service Workers<br />
* Making bugs actionable<br />
** Communicating with the bug reporter to ask them about the specifics of their report<br />
** Attempting to reproduce the bugs, perhaps by writing test cases<br />
** Gaining an understanding of who works on what in DOM, to be able to get the right eyes on bugs<br />
** Providing regression ranges and ideally identifying the commit that regressed something<br />
** Using various debugging tools (such as the built-in devtools, gdb, address sanitizer, rr, etc.) to gain more information on bugs<br />
* 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<br />
<br />
; Documentation<br />
* [https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model MDN]<br />
* How to build Nightly (Developer build of Firefox)<br />
** If you don't have mercurial installed, follow instructions to do so here: https://developer.mozilla.org/en-US/docs/Installing_Mercurial<br />
** 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<br />
* How to setup git.<br />
** get and install git from: http://www.git-scm.com/downloads<br />
*** (optional) You may also want to use a git GUI. Here's a popular version: GitHub from http://www.git-scm.com/downloads/guis.<br />
* Get the web-platform-tests and run them from the browser<br />
** With git is installed, in a terminal, run "git clone https://github.com/w3c/web-platform-tests.git"<br />
** Complete instructions for running the tests from the browser are here: https://github.com/w3c/web-platform-tests/blob/master/README.md<br />
* Run the web-platform-tests of the Nightly build.<br />
** Instructions are here: https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/README.md<br />
** For example, to run the dom javascript tests:<br />
*** 1. <hg pull and update your mozilla-central - steps here depend on how you set up your mozilla-central directory><br />
*** 2. cd <mozilla-central><br />
*** 3. ./mach build (./mach clobber may be required)<br />
*** 4. ./mach web-platform-tests --test-type=testharness --include=dom<br />
* How to bisect<br />
** 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.<br />
* [https://wiki.mozilla.org/WebAPI wiki]<br />
<br />
; Mailing Lists<br />
* mozilla.dev.platform<br />
* mozilla.dev.webapi<br />
<br />
= Meetings =<br />
== Kickoff ==<br />
Good starting points: [https://etherpad.mozilla.org/qa-dom-strategy etherpad]<br />
* tracking down regression ranges for intermittents (Ehsan will need info us on some bugs)<br />
* web platform tests: [http://testthewebforward.org/docs/ docs], [https://github.com/w3c/web-platform-tests/ repo] - start with reaching out to ms2ger/jgraham to find a good-first-issue to work on (DOM, HTML)<br />
* incoming triage<br />
** interesting to see what the volume of bug work is per sub-component<br />
** moving bugs from DOM:Core General to something more appropriate<br />
** consult bz's [https://etherpad.mozilla.org/WhatToDoWithIncomingDOMBugs etherpad]<br />
* community<br />
** work with ms2ger to find ways we can involve community<br />
<br />
Not discussed:<br />
* outgoing triage<br />
* features<br />
<br />
Next Steps:<br />
* Anthony to email team about outgoing triage (testing fixes or making sure fixes have sufficient coverage), features (what we need to be paying attention to), and incoming bug triage (All of DOM -1m to start then 24hr going forward, if load becomes too big we'll prioritize subcomponents and seek to involve community to pick up the slack)<br />
* Ehsan to needinfo us on regression window wanted bugs<br />
* Tracy & Anthony select some work from web platform tests<br />
* Tracy & Anthony to figure out goals and document (review *this* document as well)<br />
* Set up a triage meeting for the DOM team to go through to teach us what to do for different bugs<br />
<br />
= Sprint 3=<br />
* Anthony to mock up something with unconfirmed bugs<br />
* Get DOM team (Andrew and whoever else) to review benchmarks and metrics from bugzilla<br />
* Tracy to set up bug triage<br />
* Tracy to document the bug workflow w.r.t. verification - when do we verify a bug</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Electrolysis&diff=1051460QA/Electrolysis2015-01-29T19:35:25Z<p>Ctalbert: /* 2015 work */</p>
<hr />
<div>{{TOC right}} <br />
This is the test plan for [[Electrolysis]], also referred to as the e10s project or "multiprocess". With e10s enabled, Firefox content runs in a different process than the browser itself. This will help improve performance and security. Our goals in testing are to identify and communicate problems, and to be able to give a recommendation for when e10s may be ready to stay on by default for non-Nightly channels. <br />
<br />
=People=<br />
* Juan Becerra - QA lead<br />
* Liz Henry<br />
* [https://wiki.mozilla.org/Electrolysis#People e10s team]<br />
<br />
= Goal =<br />
Help E10S to achieve the same level of quality as non-e10s nightly Firefox by the time it goes to beta.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Define and establish baseline quality for e10s vs. non-e10s versions in terms of stability and memory footprint.<br />
# Identify and help triage bugs to address the quality gap<br />
# Define quality requirements for ship to aurora/dev edition<br />
# Work to identify areas of unknown bugs and risk by experimenting with expanding automated test coverage to previously untested platforms required for ship to aurora/dev edition.<br />
<br />
===How to test e10s===<br />
<br />
Please test e10s in [https://nightly.mozilla.org/ Nightly]. <br />
<br />
To enable e10s, check the "Enable e10s" or "multiprocess" box in about:preferences, and restart Nightly. <br />
If you have any problems or questions, drop by #e10s on IRC.<br />
<br />
; Reporting bugs<br />
When you find a problem, please report a bug. Please include the word "[e10s]" in the summary and set the "tracking-e10s" flag to '?' to ensure your bugs get triaged. (If you are certain a bug is present with e10s enabled, but not present with it turned off.)<br />
<br />
; Identifying e10s crashes<br />
Find and file e10s crashes by searching crash-stats for reports that include [https://crash-stats.mozilla.com/search/?dom_ipc_enabled=__true__&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform domipcenabled]. <br />
<br />
; Testing addons<br />
You can test popular addons from this list: http://arewee10syet.com<br />
<br />
==Status==<br />
===Milestones===<br />
Check the tracking-e10s field. ? means it needs triage.<br />
* Milestone 1: e10s is useable by average Nightly users. {{Bug|997456}}<br />
* m4: high priority, needs to be fixed asap<br />
* m6: blocking uplift to aurora.<br />
* m8: blocking uplift to beta. <br />
* +: tracking-e10s+ blocks uplift to release.<br />
* later: this bug has been triaged, and will not block release.<br />
<br />
;Releases<br />
Goals for releases so far:<br />
* Firefox 36: enable e10s by default in Nightly, then disabled in Aurora.<br />
* Firefox 37: (Nov. 24) e10s enabled by default in Nightly.<br />
* Firefox 38: This may end up being the target version for e10s to ride the trains to release.<br />
<br />
== Readiness ==<br />
Testing e10s really means testing all the functionality of Firefox. <br />
There are some key areas in a [https://wiki.mozilla.org/QA/Electrolysis/Feature_checklist feature checklist] where QA feature owners have expertise in testing, or where we think it will be useful to focus exploratory testing, along with our test coverage of each feature.<br />
Here are our current feature testing priorities. <br />
<br />
Current features to explore:<br />
* Developer Tools<br />
Do manual and exploratory testing. Report bugs, and associate them with the Dev Tools e10s tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=875871<br />
* Session store<br />
<br />
==Triage==<br />
The [[Electrolysis]] team meets regularly to triage bugs which are tagged ''tracking-e10s:?''. (TODO: add meeting times)<br />
<br />
* Top priority right now: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m4+]<br />
* These bugs block e10s moving to Aurora: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m6+]<br />
* These bugs block e10s moving to Beta: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=8 tracking-e10s:m8+]<br />
<br />
;Blocking Aurora ride (m4)<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,status,component,op_sys",<br />
"f1":"cf_tracking_e10s",<br />
"o1":"substring",<br />
"v1":"4"<br />
}<br />
</bugzilla><br />
<br />
==Triage incoming bugs to look for likely e10s issues==<br />
Once e10s is enabled by default on Nightly, we should see an influx of e10s bugs. <br />
<br />
How can we tell they may be e10s related? We will need to evaluate incoming bugs in Nightly with e10s turned on and turned off. Anything that is e10s related should get a whiteboard tag and we may also want to rate them for severity or mark them as blockers. We can ask bug reporters to check in about:support and search for the word "multiprocess" (which means e10s is on).<br />
<br />
If you are able to confirm a bug and can tell it is an e10s issue,<br />
please nominate the bug for the e10s tracking flag.<br />
<br />
Incoming bugs on Nightly 36, not marked with a tracking-e10s flag yet: https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591695&o1=isempty&o2=notsubstring&query_format=advanced&f2=short_desc&bug_status=UNCONFIRMED&bug_status=NEW&version=36%20Branch&version=36%20Branch&v2=intermittent&product=Core&product=Firefox&product=Toolkit<br />
<br />
==QA wanted==<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"whiteboard":"qawanted"<br />
}<br />
</bugzilla><br />
<br />
<br />
==Fixed bug triage==<br />
e10s bugs marked as RESOLVED FIXED. <br />
<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys,priority,severity,cf_qa_whiteboard",<br />
"resolution":"FIXED",<br />
"status":"RESOLVED",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"f1":"cf_qa_whiteboard",<br />
"o1":"nowords",<br />
"v1":"qa"<br />
}<br />
</bugzilla><br />
<br />
==2015 work==<br />
Q1 strategy and goals for QA: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
; e10s test metrics <br />
* Tests skipped in manifests: 225 skipped under e10s. 173 have bugs associated. <br />
* some mochitest-plain-e10s and mochitest-browser-chrome-e10s tests are enabled http://brasstacks.mozilla.com/testreports/weekly/2015-01-04.informant-report.html <br />
** mochitest-browser-chrome-e10s: linux-opt and linux64-opt have 58% of the bc tests enabled.<br />
** mochitest-plain-e10s: linux-debug: 79%. linux-opt: 80%. linux-64-debug: 79% linux64-opt: 80%<br />
* bug filed to turn more test "buckets" on for various platforms (that are green on [https://treeherder.mozilla.org/#/jobs?repo=holly holly] after a recent merge): https://bugzilla.mozilla.org/show_bug.cgi?id=1122901<br />
<br />
;Stability metrics.<br />
* Current crash rate in Nightly for e10s on vs. off. <br />
* Browser process crash rate<br />
* Content process crash rate<br />
* (What % of this are startup crashes?)<br />
* (Average uptime between crashes/ mean time between failure) <br />
* We want to aim for at least a 7-8% crash rate before moving to Aurora.<br />
* Could we get MTBF for non-e10s nightly (prior release, perhaps?), e10s enabled, and content crashes<br />
* Startup crashes as well.</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Projects/Project_Template&diff=1051120QA/Projects/Project Template2015-01-28T14:57:32Z<p>Ctalbert: Created page with "= Name of Project = Description: Goal of feature: Why is this important: Developer Contacts: QA Mentors: == Basics == * Tracking Bug: * Release schedule: number, date * IRC c..."</p>
<hr />
<div>= Name of Project =<br />
Description:<br />
Goal of feature:<br />
Why is this important:<br />
Developer Contacts:<br />
QA Mentors:<br />
<br />
== Basics ==<br />
* Tracking Bug:<br />
* Release schedule: number, date<br />
* IRC channel for quesitons<br />
* Mailing list (if applicable)<br />
* Prefs to enable it (if applicable)<br />
* Product/Engineering/Planning documents: (if any)<br />
<br />
=== Risk Assessment ===<br />
Analyze the risk this feature poses to the rest of the product's quality if it is created poorly<br />
<br />
== Basic use cases ==<br />
Describe the basic level of use cases that the system must support to be considered "complete" in terms of what should be delivered. These are likely covered by automation, verify that this is the case<br />
<br />
== Interaction/Functional use cases ==<br />
describe interaction with other systems here - this is where we will always find the most bugs<br />
<br />
== One and Done Tasks ==<br />
<br />
== MozTrap Testcases ==<br />
<br />
== Related/Dependent Features and Teams ==<br />
Add in dependent features and teams here</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Embedded_Teams&diff=1051105QA/Embedded Teams2015-01-28T14:35:42Z<p>Ctalbert: /* The Hot List */</p>
<hr />
<div>For the core Firefox and Platform QA teams we are using an embedding strategy where we have embedded QA engineers alongside engineers in specific functional teams. We are doing this to:<br />
# Improve the scope and depth of quality engineering in these areas<br />
# Provide more focus and development more technical acumen on QA<br />
# Identify strategic areas where involvement results in better overall quality across the board to best use the small number of people we have<br />
<br />
== Embedded Areas ==<br />
<br />
The areas where we are working are:<br />
* [[QA/Platform/DOM | DOM team (Tracy & Ashughes)]]<br />
* [[QA/Electrolysis | E10S (multi-process) team (Juanb & Lizzard)]]<br />
* [[QA/Security | Security and Privacy team (Kjoziwiak & Mwobensmith)]]<br />
* [[QA/Media | Media and Video team (Spolk, Marcia, and Maja)]]<br />
* [[QA/Fennec| Firefox for Android (AaronMT & Kbrosnan)]]<br />
* Overall QA Releases, Quality Programs, and Risk: Kairo & Mschifer<br />
<br />
== Non-Embedded Areas ==<br />
<br />
There are of course other areas that we cannot cover to the degree we would like to and currently have no one embedded in these teams:<br />
* Graphics<br />
* Firefox Front-end<br />
* Developer Tools<br />
* Networking<br />
* JavaScript<br />
<br />
== The Hot List ==<br />
As a result there are things that will fall through the cracks. We are working quite hard to analyze the risk of everything that falls through the cracks and ensure that risk is mitigated through some means (contributor, contractor, staff, and/or automation). We will maintain the below list for things that are currently in this zone.<br />
{|class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 20%" | Project<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Quality Risk<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Schedule<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Contributor Friendliness<br />
| style="font-weight: bold; background: #DDD; width: 50%" | Next Step/Notes<br />
|-<br />
| [[QA/Projects//Reading List|Reading List (desktop)]]<br />
| Medium<br />
| 38?<br />
| 0<br />
| <br />
* Needs assessment<br />
* Create project wiki page<br />
* Analyze deliverables and scope<br />
|-<br />
| [[QA/Projects/Password Manager|Password Manager (desktop)]]<br />
| High<br />
| ?<br />
| 0<br />
| <br />
* Needs assessment<br />
* Marked high because for years our password system (master pass/no master pass) have caused untold headache with implementations of these kinds of things<br />
* Create project wiki page<br />
* Analyze deliverables and scope<br />
|-<br />
| ios product<br />
| High<br />
| ?<br />
| -1<br />
| <br />
* Marked high because we are building our own browser UX for this effort<br />
* Marked negative contributor friendly because of difficulty of beta/pre-release programs available to iOS users<br />
* Also due to the fact that it is not clear we will work on this<br />
* Marked negative due to requirement for devices<br />
* Analyze how well and how much relevant QA can be done on simulators<br />
* Create plan<br />
|-<br />
| [[QA/Projects/win64|windows 64 bit builds]]<br />
| low<br />
| 37/38<br />
| 0<br />
| <br />
* We have excellent automation here and have had nightlies run on 64 bit builds for some time<br />
* Our existing update automation will still work<br />
* We might be able to do this entirely automated<br />
* Could ship in 37 or 38 depending on where the demand lies for this<br />
|-<br />
| [[QA/Projects/Geolocation Service|Geolocation Service Changes]]<br />
| medium<br />
| ?<br />
| 0<br />
| <br />
* Need to create the wiki page for contribution this is a prime target for contributor support because we need people in many locations testing the accuracy of the new geo system<br />
* Medium quality risk only because there are a fair number of location dependent web sites on mobile systems that will depend on this feature working (though if we are on a mobile device do we use the device's GPS, short circuiting the problem? TODO: Investigate this<br />
|-<br />
| [[QA/Projects/Addon Signing|Addon Signing]]<br />
| medium<br />
| ?<br />
| 0<br />
| <br />
* Need to create contributor wiki page for involvement<br />
* Should be imminently testable and crowd-source-able.<br />
* There is a long tail of addons, but we can divide and conquer by considering classes of addons<br />
|-<br />
| [[QA/Projects/Network Predictor|Network Predictor]]<br />
| high<br />
| 38<br />
| -1<br />
|<br />
* This was identified late in the release cycle as a problem last time it landed<br />
* We need eyes on this sooner rather than later to ensure that it does not regress performance<br />
* The speed with which we need to act coupled with the low level nature of this system makes it not as attractive an option for contributor review<br />
* Need to create test plan wiki<br />
|}</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Embedded_Teams&diff=1051101QA/Embedded Teams2015-01-28T14:22:15Z<p>Ctalbert: /* The Hot List */</p>
<hr />
<div>For the core Firefox and Platform QA teams we are using an embedding strategy where we have embedded QA engineers alongside engineers in specific functional teams. We are doing this to:<br />
# Improve the scope and depth of quality engineering in these areas<br />
# Provide more focus and development more technical acumen on QA<br />
# Identify strategic areas where involvement results in better overall quality across the board to best use the small number of people we have<br />
<br />
== Embedded Areas ==<br />
<br />
The areas where we are working are:<br />
* [[QA/Platform/DOM | DOM team (Tracy & Ashughes)]]<br />
* [[QA/Electrolysis | E10S (multi-process) team (Juanb & Lizzard)]]<br />
* [[QA/Security | Security and Privacy team (Kjoziwiak & Mwobensmith)]]<br />
* [[QA/Media | Media and Video team (Spolk, Marcia, and Maja)]]<br />
* [[QA/Fennec| Firefox for Android (AaronMT & Kbrosnan)]]<br />
* Overall QA Releases, Quality Programs, and Risk: Kairo & Mschifer<br />
<br />
== Non-Embedded Areas ==<br />
<br />
There are of course other areas that we cannot cover to the degree we would like to and currently have no one embedded in these teams:<br />
* Graphics<br />
* Firefox Front-end<br />
* Developer Tools<br />
* Networking<br />
* JavaScript<br />
<br />
== The Hot List ==<br />
As a result there are things that will fall through the cracks. We are working quite hard to analyze the risk of everything that falls through the cracks and ensure that risk is mitigated through some means (contributor, contractor, staff, and/or automation). We will maintain the below list for things that are currently in this zone.<br />
{|class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 20%" | Project<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Quality Risk<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Schedule<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Contributor Friendliness<br />
| style="font-weight: bold; background: #DDD; width: 50%" | Next Step/Notes<br />
|-<br />
| Reading List (desktop)<br />
| Medium<br />
| 38?<br />
| 0<br />
| <br />
* Needs assessment<br />
* Create project wiki page<br />
* Analyze deliverables and scope<br />
|-<br />
| Password Manager (desktop)<br />
| High<br />
| ?<br />
| 0<br />
| <br />
* Needs assessment<br />
* Marked high because for years our password system (master pass/no master pass) have caused untold headache with implementations of these kinds of things<br />
* Create project wiki page<br />
* Analyze deliverables and scope<br />
|-<br />
| ios product<br />
| High<br />
| ?<br />
| -1<br />
| <br />
* Marked high because we are building our own browser UX for this effort<br />
* Marked negative contributor friendly because of difficulty of beta/pre-release programs available to iOS users<br />
* Marked negative due to requirement for devices<br />
* Analyze how well and how much relevant QA can be done on simulators<br />
* Create plan<br />
|-<br />
| windows 64 bit builds<br />
| low<br />
| 37/38<br />
| 0<br />
| <br />
* We have excellent automation here and have had nightlies run on 64 bit builds for some time<br />
* Our existing update automation will still work<br />
* We might be able to do this entirely automated<br />
* Could ship in 37 or 38 depending on where the demand lies for this<br />
|-<br />
| geolocation service changes<br />
| medium<br />
| ?<br />
| 0<br />
| <br />
* Need to create the wiki page for contribution this is a prime target for contributor support because we need people in many locations testing the accuracy of the new geo system<br />
* Medium quality risk only because there are a fair number of location dependent web sites on mobile systems that will depend on this feature working (though if we are on a mobile device do we use the device's GPS, short circuiting the problem? TODO: Investigate this<br />
|-<br />
| addon signing<br />
| medium<br />
| ?<br />
| 0<br />
| <br />
* Need to create contributor wiki page for involvement<br />
* Should be imminently testable and crowd-source-able.<br />
* There is a long tail of addons, but we can divide and conquer by considering classes of addons<br />
|-<br />
| network predictor<br />
| high<br />
| 38<br />
| -1<br />
|<br />
* This was identified late in the release cycle as a problem last time it landed<br />
* We need eyes on this sooner rather than later to ensure that it does not regress performance<br />
* The speed with which we need to act coupled with the low level nature of this system makes it not as attractive an option for contributor review<br />
* Need to create test plan wiki<br />
|}</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Embedded_Teams&diff=1051100QA/Embedded Teams2015-01-28T14:21:32Z<p>Ctalbert: </p>
<hr />
<div>For the core Firefox and Platform QA teams we are using an embedding strategy where we have embedded QA engineers alongside engineers in specific functional teams. We are doing this to:<br />
# Improve the scope and depth of quality engineering in these areas<br />
# Provide more focus and development more technical acumen on QA<br />
# Identify strategic areas where involvement results in better overall quality across the board to best use the small number of people we have<br />
<br />
== Embedded Areas ==<br />
<br />
The areas where we are working are:<br />
* [[QA/Platform/DOM | DOM team (Tracy & Ashughes)]]<br />
* [[QA/Electrolysis | E10S (multi-process) team (Juanb & Lizzard)]]<br />
* [[QA/Security | Security and Privacy team (Kjoziwiak & Mwobensmith)]]<br />
* [[QA/Media | Media and Video team (Spolk, Marcia, and Maja)]]<br />
* [[QA/Fennec| Firefox for Android (AaronMT & Kbrosnan)]]<br />
* Overall QA Releases, Quality Programs, and Risk: Kairo & Mschifer<br />
<br />
== Non-Embedded Areas ==<br />
<br />
There are of course other areas that we cannot cover to the degree we would like to and currently have no one embedded in these teams:<br />
* Graphics<br />
* Firefox Front-end<br />
* Developer Tools<br />
* Networking<br />
* JavaScript<br />
<br />
== The Hot List ==<br />
As a result there are things that will fall through the cracks. We are working quite hard to analyze the risk of everything that falls through the cracks and ensure that risk is mitigated through some means (contributor, contractor, staff, and/or automation). We will maintain the below list for things that are currently in this zone.<br />
{|class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 20%" | Project<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Quality Risk<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Schedule<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Contributor Friendliness<br />
| style="font-weight: bold; background: #DDD; width: 50%" | Next Step/Notes<br />
|-<br />
| Reading List (desktop)<br />
| Medium<br />
| 38?<br />
| 0<br />
| <br />
* Needs assessment<br />
* Create project wiki page<br />
* Analyze deliverables and scope<br />
|-<br />
| Password Manager (desktop)<br />
| High<br />
| ?<br />
| 0<br />
| <br />
* Needs assessment<br />
* Marked high because for years our password system (master pass/no master pass) have caused untold headache with implementations of these kinds of things<br />
* Create project wiki page<br />
* Analyze deliverables and scope<br />
|-<br />
| ios product<br />
| High<br />
| ?<br />
| -1<br />
| <br />
* Marked high because we are building our own browser UX for this effort<br />
* Marked negative contributor friendly because of difficulty of beta/pre-release programs available to iOS users<br />
* Marked negative due to requirement for devices<br />
* Analyze how well and how much relevant QA can be done on simulators<br />
* Create plan<br />
|-<br />
| windows 64 bit builds<br />
| low<br />
| 37/38<br />
| 0<br />
| <br />
* We have excellent automation here and have had nightlies run on 64 bit builds for some time<br />
* Our existing update automation will still work<br />
* We might be able to do this entirely automated<br />
* Could ship in 37 or 38 depending on where the demand lies for this<br />
|-<br />
| geolocation service changes<br />
| medium<br />
| ?<br />
| 0<br />
| <br />
* Need to create the wiki page for contribution this is a prime target for contributor support because we need people in many locations testing the accuracy of the new geo system<br />
* Medium quality risk only because there are a fair number of location dependent web sites on mobile systems that will depend on this feature working (though if we are on a mobile device do we use the device's GPS, short circuiting the problem? TODO: Investigate this<br />
|-<br />
| addon signing<br />
| medium<br />
| ?<br />
| 0<br />
| <br />
* Need to create contributor wiki page for involvement<br />
* Should be imminently testable and crowd-source-able.<br />
* There is a long tail of addons, but we can divide and conquer by considering classes of addons<br />
|-<br />
| network predictor<br />
| high<br />
| -1<br />
| <br />
* This was identified late in the release cycle as a problem last time it landed<br />
* We need eyes on this sooner rather than later to ensure that it does not regress performance<br />
* The speed with which we need to act coupled with the low level nature of this system makes it not as attractive an option for contributor review<br />
* Need to create test plan wiki<br />
|}</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Electrolysis&diff=1050942QA/Electrolysis2015-01-27T22:59:10Z<p>Ctalbert: </p>
<hr />
<div>{{TOC right}} <br />
This is the test plan for [[Electrolysis]], also referred to as the e10s project or "multiprocess". With e10s enabled, Firefox content runs in a different process than the browser itself. This will help improve performance and security. Our goals in testing are to identify and communicate problems, and to be able to give a recommendation for when e10s may be ready to stay on by default for non-Nightly channels. <br />
<br />
=People=<br />
* Juan Becerra - QA lead<br />
* Liz Henry<br />
* [https://wiki.mozilla.org/Electrolysis#People e10s team]<br />
<br />
= Goal =<br />
Help E10S to achieve the same level of quality as non-e10s nightly Firefox by the time it goes to beta.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Define and establish baseline quality for e10s vs. non-e10s versions in terms of stability and memory footprint.<br />
# Identify and help triage bugs to address the quality gap<br />
# Define quality requirements for ship to aurora/dev edition<br />
# Work to identify areas of unknown bugs and risk by experimenting with expanding automated test coverage to previously untested platforms required for ship to aurora/dev edition.<br />
<br />
===How to test e10s===<br />
<br />
Please test e10s in [https://nightly.mozilla.org/ Nightly]. <br />
<br />
To enable e10s, check the "Enable e10s" or "multiprocess" box in about:preferences, and restart Nightly. <br />
If you have any problems or questions, drop by #e10s on IRC.<br />
<br />
; Reporting bugs<br />
When you find a problem, please report a bug. Please include the word "[e10s]" in the summary and set the "tracking-e10s" flag to '?' to ensure your bugs get triaged. (If you are certain a bug is present with e10s enabled, but not present with it turned off.)<br />
<br />
; Identifying e10s crashes<br />
Find and file e10s crashes by searching crash-stats for reports that include [https://crash-stats.mozilla.com/search/?dom_ipc_enabled=__true__&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform domipcenabled]. <br />
<br />
; Testing addons<br />
You can test popular addons from this list: http://arewee10syet.com<br />
<br />
==Status==<br />
===Milestones===<br />
Check the tracking-e10s field. ? means it needs triage.<br />
* Milestone 1: e10s is useable by average Nightly users. {{Bug|997456}}<br />
* m4: high priority, needs to be fixed asap<br />
* m6: blocking uplift to aurora.<br />
* m8: blocking uplift to beta. <br />
* +: tracking-e10s+ blocks uplift to release.<br />
* later: this bug has been triaged, and will not block release.<br />
<br />
;Releases<br />
Goals for releases so far:<br />
* Firefox 36: enable e10s by default in Nightly, then disabled in Aurora.<br />
* Firefox 37: (Nov. 24) e10s enabled by default in Nightly.<br />
* Firefox 38: This may end up being the target version for e10s to ride the trains to release.<br />
<br />
== Feature checklist ==<br />
Testing e10s really means testing all the functionality of Firefox. <br />
Here are some key areas where QA feature owners have expertise in testing, or where we think it will be useful to focus exploratory testing, along with our test coverage of each feature. The last column is QA's ongoing assessment of each feature's readiness to ride the trains from Nightly onward. <br />
<br />
{| class="fullwidth-table"<br />
| style="background:#EFEFEF; width:20%" | '''Feature'''<br />
| style="background:#EFEFEF; width:20%" | '''Tests'''<br />
| style="background:#EFEFEF; width:15%" | '''Bug list or meta bug'''<br />
| style="background:#EFEFEF; width:15%" | '''Automated Coverage?'''<br />
| style="background:#EFEFEF; width:15%" | '''Tested in Nightly?'''<br />
| style="background:#EFEFEF; width:15%" | '''Ready for Aurora?'''<br />
|-<br />
|[https://wiki.mozilla.org/QA/Add-ons Add-ons] (including extensions and themes)<br />
| http://mzl.la/1tkYGYc<br />
| http://mzl.la/1scWxII {{Bug|905436}}<br />
|<br />
| {{Yes}}<br />
| {{No}}<br />
|- <br />
|App update <br />
| <br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|[https://wiki.mozilla.org/QA/Audio_Video Audio/Video]<br />
|http://mzl.la/10qFhdq<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Crash reporting <br />
|http://mzl.la/1zmceqN<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|[https://wiki.mozilla.org/QA/Places Bookmarks and History]<br />
|http://mzl.la/1sc52DO<br />
| {{Bug|1067042}}<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Context menus<br />
|<br />
|{{Bug|1060070}}<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Crash reporting<br />
|<br />
|{{Bug|929045}}<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [https://wiki.mozilla.org/QA/Developer_Tools Developer Tools]<br />
| http://mzl.la/1scXOiZ<br />
| Meta:{{Bug|875871}}<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [[https://wiki.mozilla.org/QA/Firefox:Download_Manager Download Manager]<br />
| http://goo.gl/JTpbyM<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| Doorhangers and notifications: password, location, plugins, pop-up blocking, others<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|File system interactions<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Downloading files, running files (installers)<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Offline cache<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|File picker (for upload in several sites)<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Find in page<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Forget button<br />
|http://mzl.la/10qA3OR<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Fullscreen video<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [https://wiki.mozilla.org/QA/Games Games] (Marketplace Games & Apps)<br />
|http://mzl.la/1D0AI5D<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Geolocation <br />
|http://mzl.la/1t6NEpA<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Graphics<br />
|http://mzl.la/1oxOQlL<br />
|Meta:{{Bug|993639}}<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Hello (aka Loop)<br />
|<br />
|<br />
|<br />
| {{no}}<br />
| {{no}}<br />
|-<br />
|Keyboard shortcuts (on web apps)<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|[https://wiki.mozilla.org/QA/Location_Bar Location Bar]<br />
|http://mzl.la/1xcJRWz<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| Offline cache<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [https://wiki.mozilla.org/QA/Plugins Plugins]<br />
| http://mzl.la/1FINt90<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Private browsing <br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| Password Manager<br />
|http://mzl.la/1wmF59W<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| Persona<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [https://wiki.mozilla.org/QA/Printing Printing]<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [https://wiki.mozilla.org/Show_PDF_Inline/Test_Plan PDF Viewer]<br />
|http://mzl.la/1wmnNtD<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Save as menu<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [https://wiki.mozilla.org/QA/Session_Restore Session Store]<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| Spell checking<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [https://wiki.mozilla.org/QA/Shumway Shumway]<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|Social API<br />
|<br />
| {{Bug|915546}}<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [https://wiki.mozilla.org/QA/Sync Sync]<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| Tab management (drag and drop)<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| Toolbar customization<br />
|http://mzl.la/12j37IV<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| Touch interfaces (?)<br />
|<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [https://wiki.mozilla.org/QA/Translation Translation]<br />
|http://mzl.la/1D0QPQu<br />
|<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
| [ WebRTC/plugins/media]<br />
|<br />
|meta:{{Bug|849746}}<br />
|<br />
| {{No}}<br />
| {{No}}<br />
|-<br />
|}<br />
<br />
==Triage==<br />
The [[Electrolysis]] team meets regularly to triage bugs which are tagged ''tracking-e10s:?''. (TODO: add meeting times)<br />
<br />
* Top priority right now: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m4+]<br />
* These bugs block e10s moving to Aurora: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=4 tracking-e10s:m6+]<br />
* These bugs block e10s moving to Beta: [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591600&o1=substring&resolution=---&query_format=advanced&v1=8 tracking-e10s:m8+]<br />
<br />
;Blocking Aurora ride (m4)<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,status,component,op_sys",<br />
"f1":"cf_tracking_e10s",<br />
"o1":"substring",<br />
"v1":"4"<br />
}<br />
</bugzilla><br />
<br />
==Triage incoming bugs to look for likely e10s issues==<br />
Once e10s is enabled by default on Nightly, we should see an influx of e10s bugs. <br />
<br />
How can we tell they may be e10s related? We will need to evaluate incoming bugs in Nightly with e10s turned on and turned off. Anything that is e10s related should get a whiteboard tag and we may also want to rate them for severity or mark them as blockers. We can ask bug reporters to check in about:support and search for the word "multiprocess" (which means e10s is on).<br />
<br />
If you are able to confirm a bug and can tell it is an e10s issue,<br />
please nominate the bug for the e10s tracking flag.<br />
<br />
Incoming bugs on Nightly 36, not marked with a tracking-e10s flag yet: https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_e10s&list_id=11591695&o1=isempty&o2=notsubstring&query_format=advanced&f2=short_desc&bug_status=UNCONFIRMED&bug_status=NEW&version=36%20Branch&version=36%20Branch&v2=intermittent&product=Core&product=Firefox&product=Toolkit<br />
<br />
==QA wanted==<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"whiteboard":"qawanted"<br />
}<br />
</bugzilla><br />
<br />
<br />
==Fixed bug triage==<br />
e10s bugs marked as RESOLVED FIXED. <br />
<br />
<bugzilla><br />
{<br />
"include_fields":"id,summary,component,op_sys,priority,severity,cf_qa_whiteboard",<br />
"resolution":"FIXED",<br />
"status":"RESOLVED",<br />
"short_desc":"e10s",<br />
"short_desc_type":"allwordssubstr",<br />
"f1":"cf_qa_whiteboard",<br />
"o1":"nowords",<br />
"v1":"qa"<br />
}<br />
</bugzilla><br />
<br />
==2015 work==<br />
Q1 strategy and goals for QA: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
January: e10s test metrics.<br />
* Tests skipped in manifests: 225 skipped under e10s. 173 have bugs associated. <br />
* some mochitest-plain-e10s and mochitest-browser-chrome-e10s tests are enabled http://brasstacks.mozilla.com/testreports/weekly/2015-01-04.informant-report.html <br />
** mochitest-browser-chrome-e10s: linux-opt and linux64-opt have 58% of the bc tests enabled.<br />
** mochitest-plain-e10s: linux-debug: 79%. linux-opt: 80%. linux-64-debug: 79% linux64-opt: 80%<br />
* bug filed to turn more test "buckets" on for various platforms (that are green on [https://treeherder.mozilla.org/#/jobs?repo=holly holly] after a recent merge): https://bugzilla.mozilla.org/show_bug.cgi?id=1122901</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Platform/DOM&diff=1050940QA/Platform/DOM2015-01-27T22:54:00Z<p>Ctalbert: </p>
<hr />
<div>= Summary =<br />
This page documents the strategy for testing and ensuring the quality of Gecko's DOM code.<br />
<br />
; QA Contacts<br />
* [mailto:ahughes@mozilla.com Anthony Hughes] (IRC: ashughes)<br />
* [mailto:twalker@mozilla.com Tracy Walker] (IRC: tracy)<br />
<br />
= Goal =<br />
Support DOM efforts to bring firefox back to the forefront of developer mindshare through exposing more of the web platform to community and ensuring the quality of the new features being implemented for the web platform.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Bug triage and documentation to further contributor involvement<br />
# Define and establish base-line quality metrics for DOM<br />
# [https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html Service Workers] spec coverage in web platform tests<br />
# [http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#the-picture-element Picture Tag] spec coverage in web platform tests<br />
<br />
= To Do =<br />
1) Establishing a Baseline<br />
* Define "high quality" for this project and its stakeholders, and establish metrics<br />
* Define how are bugs logged and triaged, establish metrics on bug flow<br />
* Review and document existing automated/manual test coverage<br />
* Document dependencies this code has on other components<br />
* Document prefs for enabling/disabling features, default values and their effect<br />
* Document special hardware, software, and/or skills required to contribute<br />
* Narrow down "DOM" into a set of scoped things so we can prioritize and strategize the scopeable things<br />
<br />
2) Developing a Strategy<br />
* Identify the features and their primary use cases<br />
* Define minimum acceptance and develop smoketests to ensure that's covered<br />
* Define end-to-end tests and how those should be implemented<br />
* Define areas community can contribute, establish metrics to measure community success<br />
* Define bug triage process including how bugs are prioritized<br />
* Define the criteria for what qualifies a bug as needing QE verification<br />
* Define best practices and begin on-boarding community members to support them<br />
<br />
3) Develop an execution plan<br />
* Divide the strategy into work that can be accomplished within two weeks<br />
* Document a roadmap of what's being worked on, what's next on the list, and what's down the road<br />
* Determine how success of each sprint will be measured and make adjustments based on these measurements<br />
* Review accomplishments and setbacks at the end of each sprint<br />
<br />
4) Establish Milestones<br />
* Code not riding the trains: verify merged branches do *not* have the code and that nothing has regressed<br />
* Code riding the trains: verify automation, manual test coverage, metrics in place to qualify<br />
* Define go-no-go requirements for each branch milestone<br />
* Define any ''all hands'' testing requirements for the Beta phase<br />
<br />
= Template =<br />
; ''To be edited as necessary''<br />
<br />
== Introduction ==<br />
; ''Brief description of the area/feature(s) covered by this document.''<br />
The primary purpose here is provide enough information about this functional area to a new person that they will be able to achieve a basic understanding of the feature and provide links to the any documentation or engineering docs for further reading is needed. If this is a new feature include which release it is targeted at.<br />
<br />
== Testing Approach ==<br />
; ''High level overview of the testing methodologies used in each type of testing done for this project (Manual and Automated)''<br />
<br />
The purpose of this section is provide guidance on how this area can be tested and what methodologies are most likely to be productive. For example when testing WebRTC the approach for manual testing would be to initiate calls connections between to clients and verify audio and video quality. The automated approach would be to use predictable data sources for audio and video steams allowing you to preform data analysis on the call statistics. Additionally you will want to provide some guidance on what can and can not be tested. <br />
<br />
Include:<br />
* Examples of things to watch for. <br />
* What are some of common errors and issues that this testing is targeted at finding <br />
* Filing Bugs <br />
** How are bugs reported. <br />
** What component(s) should they be filed under <br />
** Define keywords, whiteboard tags and other flags or verbage that is expected to be used when reporting bugs <br />
<br />
== Get Involved ==<br />
; ''How can volunteers and community members become involved in this project.''<br />
* Links to One and Done tasks <br />
* Links to Moztrap tests<br />
* Good First Verify in bugzilla <br />
* Links to any tutorials and other QA introductory material <br />
* Contact information and Meetings schedules and information on how to join <br />
<br />
== Requirements ==<br />
; ''What are the minimum requirements for becoming involved (Hardware, Software, Skills)''<br />
* Describe the required test environment and provide instructions on how to create it. <br />
* If special skills are required, provide links to any tutorials that may be available on the subject.<br />
* If special hardware is required, provide steps on how to verify that the testers systems meet the minimum requirements.<br />
<br />
== Related Prefs ==<br />
; ''Define any preferences or about:config options that are related to the behavior of this area''<br />
Describe what pref or option does and what values should be used and how they will change the behavior of the browser. Be sure to include what the default value should be.<br />
<br />
== Related Features ==<br />
; ''What other features are either directly related too or can be affected by changes made to this feature.'' <br />
<br />
For instance, changes to the javascript engine can have effects on emscipten and asm.js. WebRTC has dependencies on graphics (Open H.264) and Networking. <br />
<br />
== Test Cases ==<br />
; ''Define the test cases required to test this feature/area.''<br />
Include which tests can and should be automated, which framework used and how often the should be executed. * Provide link to repository(ies) for automated tests. <br />
* Smoke<br />
* Describe basic smoke tests required to prove minimum acceptance <br />
* Functional <br />
* List each major functional area to be tested and basic concepts for testing <br />
* End-to-end User Stories <br />
* Describe primary use cases <br />
* Exploratory<br />
* Describe some related areas and user stories that may be useful to explore <br />
<br />
== Bug Triage ==<br />
; ''Methodology for bug triage''<br />
* Criteria for determining priority <br />
* Minimum criteria for internal verification (qe-verify+)<br />
<br />
; Queries<br />
* intermittent failures: ?<br />
* [http://mzl.la/1wSHQgk unconfirmed general]: move bugs into the appropriate sub-component<br />
* [http://mzl.la/1BFmneX unconfirmed all]: see if there's any bugs that need reproducing<br />
<br />
== Risks ==<br />
; ''What are the primary areas of risk involved in this area.'' <br />
For example Graphics has the risk of not being to have a broad enough test bed to provide coverage for edge case testing and may result in unexpected behavior when released to a wider audience. <br />
<br />
== Reporting and Status ==<br />
; ''Describe how are test results reported and provide links to any automated test reports or dashboards.''<br />
* List milestones and current progress <br />
* Include bug queries for tracked bugs <br />
* Sign-off status for each release tested.<br />
<br />
= Ramp Up =<br />
; People<br />
* Lead: Andrew Overholt<br />
* Mentors: Ehsan Akhgari, Anne van Kesteren, Josh Matthews, Boris Zbarsky<br />
<br />
; [https://wiki.mozilla.org/Platform/Roadmap#DOM 2015 Roadmap]<br />
* [https://github.com/w3c/web-platform-tests Web Platform Tests]<br />
** Automated cross-browser testing of features that involve UI (e.g. permission UI)<br />
* Web Components<br />
* Service Workers<br />
* Making bugs actionable<br />
** Communicating with the bug reporter to ask them about the specifics of their report<br />
** Attempting to reproduce the bugs, perhaps by writing test cases<br />
** Gaining an understanding of who works on what in DOM, to be able to get the right eyes on bugs<br />
** Providing regression ranges and ideally identifying the commit that regressed something<br />
** Using various debugging tools (such as the built-in devtools, gdb, address sanitizer, rr, etc.) to gain more information on bugs<br />
* 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<br />
<br />
; Documentation<br />
* [https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model MDN]<br />
* How to build Nightly (Developer build of Firefox)<br />
** If you don't have mercurial installed, follow instructions to do so here: https://developer.mozilla.org/en-US/docs/Installing_Mercurial<br />
** 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<br />
* How to setup git.<br />
** get and install git from: http://www.git-scm.com/downloads<br />
*** (optional) You may also want to use a git GUI. Here's a popular version: GitHub from http://www.git-scm.com/downloads/guis.<br />
* Get the web-platform-tests and run them from the browser<br />
** With git is installed, in a terminal, run "git clone https://github.com/w3c/web-platform-tests.git"<br />
** Complete instructions for running the tests from the browser are here: https://github.com/w3c/web-platform-tests/blob/master/README.md<br />
* Run the web-platform-tests of the Nightly build.<br />
** Instructions are here: https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/README.md<br />
** For example, to run the dom javascript tests:<br />
*** 1. <hg pull and update your mozilla-central - steps here depend on how you set up your mozilla-central directory><br />
*** 2. cd <mozilla-central><br />
*** 3. ./mach build (./mach clobber may be required)<br />
*** 4. ./mach web-platform-tests --test-type=testharness --include=dom<br />
<br />
* How to bisect<br />
** If you are working on a bug that needs a regression range and you have 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. <br />
* [https://wiki.mozilla.org/WebAPI wiki]<br />
<br />
; Mailing Lists<br />
* mozilla.dev.platform<br />
* mozilla.dev.webapi<br />
<br />
= Meetings =<br />
== Kickoff ==<br />
Good starting points: [https://etherpad.mozilla.org/qa-dom-strategy etherpad]<br />
* tracking down regression ranges for intermittents (Ehsan will need info us on some bugs)<br />
* web platform tests: [http://testthewebforward.org/docs/ docs], [https://github.com/w3c/web-platform-tests/ repo] - start with reaching out to ms2ger/jgraham to find a good-first-issue to work on (DOM, HTML)<br />
* incoming triage<br />
** interesting to see what the volume of bug work is per sub-component<br />
** moving bugs from DOM:Core General to something more appropriate<br />
** consult bz's [https://etherpad.mozilla.org/WhatToDoWithIncomingDOMBugs etherpad]<br />
* community<br />
** work with ms2ger to find ways we can involve community<br />
<br />
Not discussed:<br />
* outgoing triage<br />
* features<br />
<br />
Next Steps:<br />
* Anthony to email team about outgoing triage (testing fixes or making sure fixes have sufficient coverage), features (what we need to be paying attention to), and incoming bug triage (All of DOM -1m to start then 24hr going forward, if load becomes too big we'll prioritize subcomponents and seek to involve community to pick up the slack)<br />
* Ehsan to needinfo us on regression window wanted bugs<br />
* Tracy & Anthony select some work from web platform tests<br />
* Tracy & Anthony to figure out goals and document (review *this* document as well)<br />
* Set up a triage meeting for the DOM team to go through to teach us what to do for different bugs</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Platform/DOM&diff=1050935QA/Platform/DOM2015-01-27T22:49:46Z<p>Ctalbert: </p>
<hr />
<div>= Summary =<br />
This page documents the strategy for testing and ensuring the quality of Gecko's DOM code.<br />
<br />
; QA Contacts<br />
* [mailto:ahughes@mozilla.com Anthony Hughes] (IRC: ashughes)<br />
* [mailto:twalker@mozilla.com Tracy Walker] (IRC: tracy)<br />
<br />
= Strategy =<br />
Support DOM efforts to bring firefox back to the forefront of developer mindshare through exposing more of the web platform to community and ensuring the quality of the new features being implemented for the web platform.<br />
<br />
== Priorities - Q1 2015 ==<br />
# Bug triage and documentation to further contributor involvement<br />
# Define and establish base-line quality metrics for DOM<br />
# [https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html Service Workers] spec coverage in web platform tests<br />
# [http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#the-picture-element Picture Tag] spec coverage in web platform tests<br />
<br />
= To Do =<br />
1) Establishing a Baseline<br />
* Define "high quality" for this project and its stakeholders, and establish metrics<br />
* Define how are bugs logged and triaged, establish metrics on bug flow<br />
* Review and document existing automated/manual test coverage<br />
* Document dependencies this code has on other components<br />
* Document prefs for enabling/disabling features, default values and their effect<br />
* Document special hardware, software, and/or skills required to contribute<br />
* Narrow down "DOM" into a set of scoped things so we can prioritize and strategize the scopeable things<br />
<br />
2) Developing a Strategy<br />
* Identify the features and their primary use cases<br />
* Define minimum acceptance and develop smoketests to ensure that's covered<br />
* Define end-to-end tests and how those should be implemented<br />
* Define areas community can contribute, establish metrics to measure community success<br />
* Define bug triage process including how bugs are prioritized<br />
* Define the criteria for what qualifies a bug as needing QE verification<br />
* Define best practices and begin on-boarding community members to support them<br />
<br />
3) Develop an execution plan<br />
* Divide the strategy into work that can be accomplished within two weeks<br />
* Document a roadmap of what's being worked on, what's next on the list, and what's down the road<br />
* Determine how success of each sprint will be measured and make adjustments based on these measurements<br />
* Review accomplishments and setbacks at the end of each sprint<br />
<br />
4) Establish Milestones<br />
* Code not riding the trains: verify merged branches do *not* have the code and that nothing has regressed<br />
* Code riding the trains: verify automation, manual test coverage, metrics in place to qualify<br />
* Define go-no-go requirements for each branch milestone<br />
* Define any ''all hands'' testing requirements for the Beta phase<br />
<br />
= Template =<br />
; ''To be edited as necessary''<br />
<br />
== Introduction ==<br />
; ''Brief description of the area/feature(s) covered by this document.''<br />
The primary purpose here is provide enough information about this functional area to a new person that they will be able to achieve a basic understanding of the feature and provide links to the any documentation or engineering docs for further reading is needed. If this is a new feature include which release it is targeted at.<br />
<br />
== Testing Approach ==<br />
; ''High level overview of the testing methodologies used in each type of testing done for this project (Manual and Automated)''<br />
<br />
The purpose of this section is provide guidance on how this area can be tested and what methodologies are most likely to be productive. For example when testing WebRTC the approach for manual testing would be to initiate calls connections between to clients and verify audio and video quality. The automated approach would be to use predictable data sources for audio and video steams allowing you to preform data analysis on the call statistics. Additionally you will want to provide some guidance on what can and can not be tested. <br />
<br />
Include:<br />
* Examples of things to watch for. <br />
* What are some of common errors and issues that this testing is targeted at finding <br />
* Filing Bugs <br />
** How are bugs reported. <br />
** What component(s) should they be filed under <br />
** Define keywords, whiteboard tags and other flags or verbage that is expected to be used when reporting bugs <br />
<br />
== Get Involved ==<br />
; ''How can volunteers and community members become involved in this project.''<br />
* Links to One and Done tasks <br />
* Links to Moztrap tests<br />
* Good First Verify in bugzilla <br />
* Links to any tutorials and other QA introductory material <br />
* Contact information and Meetings schedules and information on how to join <br />
<br />
== Requirements ==<br />
; ''What are the minimum requirements for becoming involved (Hardware, Software, Skills)''<br />
* Describe the required test environment and provide instructions on how to create it. <br />
* If special skills are required, provide links to any tutorials that may be available on the subject.<br />
* If special hardware is required, provide steps on how to verify that the testers systems meet the minimum requirements.<br />
<br />
== Related Prefs ==<br />
; ''Define any preferences or about:config options that are related to the behavior of this area''<br />
Describe what pref or option does and what values should be used and how they will change the behavior of the browser. Be sure to include what the default value should be.<br />
<br />
== Related Features ==<br />
; ''What other features are either directly related too or can be affected by changes made to this feature.'' <br />
<br />
For instance, changes to the javascript engine can have effects on emscipten and asm.js. WebRTC has dependencies on graphics (Open H.264) and Networking. <br />
<br />
== Test Cases ==<br />
; ''Define the test cases required to test this feature/area.''<br />
Include which tests can and should be automated, which framework used and how often the should be executed. * Provide link to repository(ies) for automated tests. <br />
* Smoke<br />
* Describe basic smoke tests required to prove minimum acceptance <br />
* Functional <br />
* List each major functional area to be tested and basic concepts for testing <br />
* End-to-end User Stories <br />
* Describe primary use cases <br />
* Exploratory<br />
* Describe some related areas and user stories that may be useful to explore <br />
<br />
== Bug Triage ==<br />
; ''Methodology for bug triage''<br />
* Criteria for determining priority <br />
* Minimum criteria for internal verification (qe-verify+)<br />
<br />
; Queries<br />
* intermittent failures: ?<br />
* [http://mzl.la/1wSHQgk unconfirmed general]: move bugs into the appropriate sub-component<br />
* [http://mzl.la/1BFmneX unconfirmed all]: see if there's any bugs that need reproducing<br />
<br />
== Risks ==<br />
; ''What are the primary areas of risk involved in this area.'' <br />
For example Graphics has the risk of not being to have a broad enough test bed to provide coverage for edge case testing and may result in unexpected behavior when released to a wider audience. <br />
<br />
== Reporting and Status ==<br />
; ''Describe how are test results reported and provide links to any automated test reports or dashboards.''<br />
* List milestones and current progress <br />
* Include bug queries for tracked bugs <br />
* Sign-off status for each release tested.<br />
<br />
= Ramp Up =<br />
; People<br />
* Lead: Andrew Overholt<br />
* Mentors: Ehsan Akhgari, Anne van Kesteren, Josh Matthews, Boris Zbarsky<br />
<br />
; [https://wiki.mozilla.org/Platform/Roadmap#DOM 2015 Roadmap]<br />
* [https://github.com/w3c/web-platform-tests Web Platform Tests]<br />
** Automated cross-browser testing of features that involve UI (e.g. permission UI)<br />
* Web Components<br />
* Service Workers<br />
* Making bugs actionable<br />
** Communicating with the bug reporter to ask them about the specifics of their report<br />
** Attempting to reproduce the bugs, perhaps by writing test cases<br />
** Gaining an understanding of who works on what in DOM, to be able to get the right eyes on bugs<br />
** Providing regression ranges and ideally identifying the commit that regressed something<br />
** Using various debugging tools (such as the built-in devtools, gdb, address sanitizer, rr, etc.) to gain more information on bugs<br />
* 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<br />
<br />
; Documentation<br />
* [https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model MDN]<br />
* How to build Nightly (Developer build of Firefox)<br />
** If you don't have mercurial installed, follow instructions to do so here: https://developer.mozilla.org/en-US/docs/Installing_Mercurial<br />
** 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<br />
* How to setup git.<br />
** get and install git from: http://www.git-scm.com/downloads<br />
*** (optional) You may also want to use a git GUI. Here's a popular version: GitHub from http://www.git-scm.com/downloads/guis.<br />
* Get the web-platform-tests and run them from the browser<br />
** With git is installed, in a terminal, run "git clone https://github.com/w3c/web-platform-tests.git"<br />
** Complete instructions for running the tests from the browser are here: https://github.com/w3c/web-platform-tests/blob/master/README.md<br />
* Run the web-platform-tests of the Nightly build.<br />
** Instructions are here: https://dxr.mozilla.org/mozilla-central/source/testing/web-platform/README.md<br />
** For example, to run the dom javascript tests:<br />
*** 1. <hg pull and update your mozilla-central - steps here depend on how you set up your mozilla-central directory><br />
*** 2. cd <mozilla-central><br />
*** 3. ./mach build (./mach clobber may be required)<br />
*** 4. ./mach web-platform-tests --test-type=testharness --include=dom<br />
<br />
* How to bisect<br />
** If you are working on a bug that needs a regression range and you have 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. <br />
* [https://wiki.mozilla.org/WebAPI wiki]<br />
<br />
; Mailing Lists<br />
* mozilla.dev.platform<br />
* mozilla.dev.webapi<br />
<br />
= Meetings =<br />
== Kickoff ==<br />
Good starting points: [https://etherpad.mozilla.org/qa-dom-strategy etherpad]<br />
* tracking down regression ranges for intermittents (Ehsan will need info us on some bugs)<br />
* web platform tests: [http://testthewebforward.org/docs/ docs], [https://github.com/w3c/web-platform-tests/ repo] - start with reaching out to ms2ger/jgraham to find a good-first-issue to work on (DOM, HTML)<br />
* incoming triage<br />
** interesting to see what the volume of bug work is per sub-component<br />
** moving bugs from DOM:Core General to something more appropriate<br />
** consult bz's [https://etherpad.mozilla.org/WhatToDoWithIncomingDOMBugs etherpad]<br />
* community<br />
** work with ms2ger to find ways we can involve community<br />
<br />
Not discussed:<br />
* outgoing triage<br />
* features<br />
<br />
Next Steps:<br />
* Anthony to email team about outgoing triage (testing fixes or making sure fixes have sufficient coverage), features (what we need to be paying attention to), and incoming bug triage (All of DOM -1m to start then 24hr going forward, if load becomes too big we'll prioritize subcomponents and seek to involve community to pick up the slack)<br />
* Ehsan to needinfo us on regression window wanted bugs<br />
* Tracy & Anthony select some work from web platform tests<br />
* Tracy & Anthony to figure out goals and document (review *this* document as well)<br />
* Set up a triage meeting for the DOM team to go through to teach us what to do for different bugs</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Embedded_Teams&diff=1050932QA/Embedded Teams2015-01-27T22:36:58Z<p>Ctalbert: </p>
<hr />
<div>For the core Firefox and Platform QA teams we are using an embedding strategy where we have embedded QA engineers alongside engineers in specific functional teams. We are doing this to:<br />
# Improve the scope and depth of quality engineering in these areas<br />
# Provide more focus and development more technical acumen on QA<br />
# Identify strategic areas where involvement results in better overall quality across the board to best use the small number of people we have<br />
<br />
The areas where we are working are:<br />
* [[QA/Platform/DOM | DOM team (Tracy & Ashughes)]]<br />
* [[QA/Electrolysis | E10S (multi-process) team (Juanb & Lizzard)]]<br />
* [[QA/Security | Security and Privacy team (Kjoziwiak & Mwobensmith)]]<br />
* [[QA/Media | Media and Video team (Spolk, Marcia, and Maja)]]<br />
* [[QA/Fennec| Firefox for Android (AaronMT & Kbrosnan)]]<br />
* Overall QA Releases, Quality Programs, and Risk: Kairo & Mschifer<br />
<br />
There are of course other areas that we cannot cover to the degree we would like to and currently have no one embedded in these teams:<br />
* Graphics<br />
* Firefox Front-end<br />
* Developer Tools<br />
* Networking<br />
* JavaScript<br />
<br />
As a result there are things that will fall through the cracks. We are working quite hard to analyze the risk of everything that falls through the cracks and ensure that risk is mitigated through some means (contributor, contractor, staff, and/or automation). We will maintain the below list for things that are currently in this zone.<br />
* Reading List (desktop)<br />
* Password Manager (desktop)<br />
* ios product<br />
* windows 64 bit builds<br />
* geolocation changes<br />
* addon signing<br />
* network predictor landing</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Embedded_Teams&diff=1050931QA/Embedded Teams2015-01-27T22:34:56Z<p>Ctalbert: Created page with "For the core Firefox and Platform QA teams we are using an embedding strategy where we have embedded QA engineers alongside engineers in specific functional teams. We are doin..."</p>
<hr />
<div>For the core Firefox and Platform QA teams we are using an embedding strategy where we have embedded QA engineers alongside engineers in specific functional teams. We are doing this to:<br />
# Improve the scope and depth of quality engineering in these areas<br />
# Provide more focus and development more technical acumen on QA<br />
# Identify strategic areas where involvement results in better overall quality across the board to best use the small number of people we have<br />
<br />
The areas where we are working are:<br />
* [[QA/Platform/DOM | DOM team (Tracy & Ashughes)]]<br />
* [[QA/Electrolysis | E10S (multi-process) team (Juanb & Lizzard)]]<br />
* [[QA/Security | Security and Privacy team (Kjoziwiak & Mwobensmith)]]<br />
* [[QA/Media | Media and Video team (Spolk, Marcia, and Maja)]]<br />
* [[QA/Fennec| Firefox for Android (AaronMT & Kbrosnan)]]<br />
* Overall QA Releases, Quality Programs, and Risk: Kairo & Mschifer<br />
<br />
There are of course other areas that we cannot cover to the degree we would like to and currently have no one embedded in these teams:<br />
* Graphics<br />
* Firefox Front-end<br />
* Developer Tools<br />
* Networking<br />
* JavaScript<br />
<br />
As a result there are things that will fall through the cracks. We are working quite hard to analyze the risk of everything that falls through the cracks and ensure that risk is mitigated through some means (contributor, contractor, staff, and/or automation). We will maintain the below list for things that are currently in this zone.<br />
* Reading List (desktop)<br />
* Password Manager (desktop)<br />
* ios product<br />
* windows 64 bit builds<br />
* geolocation changes<br />
*</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting&diff=1050186QA/Team Meeting2015-01-26T04:01:15Z<p>Ctalbert: </p>
<hr />
<div>Our every 2 week meeting is open to the public. You're welcome to join.<br />
<br />
== Meeting Details ==<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Angel conference room.<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23qa irc://irc.mozilla.org:6697/#qa]<br />
<br />
* Please see below for next meeting date and previous archived meetings<br />
* [[QA/Team_Meeting/QA_Team_Template|Team Meeting Template]]<br />
* [[QA/StaffMeetings/videos| Videos of meetings]]<br />
<createbox><br />
align=left<br />
type=create<br />
preload=QA/Team_Meeting/QA_Team_Template<br />
default={{#time: Y-m-d | wednesday}}<br />
prefix=QA/Team_Meeting/QA_Team_Meeting-<br />
</createbox><br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2015 <br />
|-<br />
|<br />
* February 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-02-04|QA Team Meeting Feb 4]]<br />
* January 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-21|QA Team Meeting Jan 21]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-14|QA Team Meeting Jan 14]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-07|QA Team Meeting Jan 7]]<br />
|}<br />
<br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2014 <br />
|-<br />
|<br />
* December 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-17|QA Team Meeting Dec 17]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-10|QA Team Meeting Dec 10]]<br />
* November 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-26|QA Team Meeting Nov 26]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-19|QA Team Meeting Nov 19]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-12|QA Team Meeting Nov 12]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-05|QA Team Meeting Nov 5]]<br />
* October 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-29|QA Team Meeting Oct 29]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-22|QA Team Meeting Oct 22]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-15|QA Team Meeting Oct 15]]<br />
** QA Team Meeting Oct 08 - CANCELED<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-01|QA Team Meeting Oct 01]]<br />
*September 2014<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-24 | QA Team Meeting Sept 24]]<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-17 | QA Team Meeting Sept 17]]<br />
**[[QA/Team_Meeting/QA-Team-2014-09-10 | QA Team Meeting Sept 10]]<br />
**[[QA/Team_Meeting/QA-Team-09-03-2014 | QA Team Meeting Sept 3]]<br />
*August 2014<br />
**[[QA/StaffMeetings/QA-Staff-08-27-2014|QA-Staff-08-27-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-20-2014|QA-Staff-08-20-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-13-2014|QA-Staff-08-13-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-06-2014|QA-Staff-08-06-2014]]<br />
*July 2014<br />
** Meeting on July 30 was canceled due to QA Work Week<br />
**[[QA/StaffMeetings/QA-Staff-07-23-2014|QA-Staff-07-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-16-2014|QA-Staff-07-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-09-2014|QA-Staff-07-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-02-2014|QA-Staff-07-02-2014]]<br />
*June 2014<br />
**[[QA/StaffMeetings/QA-Staff-06-25-2014|QA-Staff-06-25-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-18-2014|QA-Staff-06-18-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-11-2014|QA-Staff-06-11-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-04-2014|QA-Staff-06-04-2014]]<br />
*May 2014<br />
**[[QA/StaffMeetings/QA-Staff-05-28-2014|QA-Staff-05-28-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-21-2014|QA-Staff-05-21-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-14-2014|QA-Staff-05-14-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-07-2014|QA-Staff-05-07-2014]]<br />
*April 2014<br />
**[[QA/StaffMeetings/QA-Staff-04-30-2014|QA-Staff-04-30-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-23-2014|QA-Staff-04-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-16-2014|QA-Staff-04-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-09-2014|QA-Staff-04-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-02-2014|QA-Staff-04-02-2014]]<br />
*March 2014<br />
**[[QA/StaffMeetings/QA-Staff-03-26-2014|QA-Staff-03-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-19-2014|QA-Staff-03-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-12-2014|QA-Staff-03-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-05-2014|QA-Staff-03-05-2014]]<br />
*February 2014<br />
**[[QA/StaffMeetings/QA-Staff-02-26-2014|QA-Staff-02-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-19-2014|QA-Staff-02-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-12-2014|QA-Staff-02-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-05-2014|QA-Staff-02-05-2014]]<br />
*January 2014<br />
**[[QA/StaffMeetings/QA-Staff-01-29-2014|QA-Staff-01-29-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-22-2014|QA-Staff-01-22-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-15-2014|QA-Staff-01-15-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-08-2014|QA-Staff-01-08-2014]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2013<br />
|-<br />
|<br />
*December<br />
**[[QA/StaffMeetings/QA-Staff-12-18-2013|QA-Staff-12-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-11-2013|QA-Staff-12-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-04-2013|QA-Staff-12-04-2013]]<br />
*November<br />
**[[QA/StaffMeetings/QA-Staff-11-27-2013|QA-Staff-11-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-20-2013|QA-Staff-11-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-13-2013|QA-Staff-11-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-06-2013|QA-Staff-11-06-2013]]<br />
*October<br />
**[[QA/StaffMeetings/QA-Staff-10-30-2013|QA-Staff-10-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-23-2013|QA-Staff-10-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-16-2013|QA-Staff-10-16-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-09-2013|QA-Staff-10-09-2013]]<br />
*Sept<br />
**[[QA/StaffMeetings/QA-Staff-09-25-2013|QA-Staff-09-25-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-18-2013|QA-Staff-09-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-11-2013|QA-Staff-09-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-04-2013|QA-Staff-09-04-2013]]<br />
*August 2013<br />
**[[QA/StaffMeetings/QA-Staff-08-28-2013|QA-Staff-08-28-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-21-2013|QA-Staff-08-21-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-14-2013|QA-Staff-08-14-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-07-2013|QA-Staff-08-07-2013]]<br />
*July 2013<br />
**[[QA/StaffMeetings/QA-Staff-07-31-2013|QA-Staff-07-31-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-24-2013|QA-Staff-07-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-17-2013|QA-Staff-07-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-10-2013|QA-Staff-07-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-03-2013|QA-Staff-07-03-2013]]<br />
*June 2013<br />
**[[QA/StaffMeetings/QA-Staff-06-26-2013|QA-Staff-06-26-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-19-2013|QA-Staff-06-19-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-12-2013|QA-Staff-06-12-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-05-2013|QA-Staff-06-05-2013]]<br />
*May 2013<br />
**[[QA/StaffMeetings/QA-Staff-05-29-2013|QA-Staff-05-29-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-22-2013|QA-Staff-05-22-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-15-2013|QA-Staff-05-15-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-08-2013|QA-Staff-05-08-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-01-2013|QA-Staff-05-01-2013]]<br />
*April 2013<br />
**[[QA/StaffMeetings/QA-Staff-04-24-2013|QA-Staff-04-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-17-2013|QA-Staff-04-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-10-2013|QA-Staff-04-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-03-2013|QA-Staff-04-03-2013]]<br />
* March 2013<br />
**[[QA/StaffMeetings/QA-Staff-03-27-2013|QA-Staff-03-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-20-2013|QA-Staff-03-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-13-2013|QA-Staff-03-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-06-2013|QA-Staff-03-06-2013]]<br />
* Febuary 2013<br />
**[[QA/StaffMeetings/QA-Staff-02-27-2013|QA-Staff-02-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-20-2013|QA-Staff-02-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-13-2013|QA-Staff-02-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-06-2013|QA-Staff-02-06-2013]]<br />
* January 2013<br />
**[[QA/StaffMeetings/QA-Staff-01-30-2013|QA-Staff-01-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-23-2013|QA-Staff-01-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-16-2013|QA-Staff-01-16-2013]]<br />
|}<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2012<br />
|-<br />
|<br />
* December 2012<br />
**[[QA/StaffMeetings/QA-Staff-12-19-2012|QA-Staff-12-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-12-2012|QA-Staff-12-12-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-05-2012|QA-Staff-12-05-2012]]<br />
* November<br />
**[[QA/StaffMeetings/QA-Staff-11-28-2012|QA-Staff-11-28-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-21-2012|QA-Staff-11-21-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-14-2012|QA-Staff-11-14-2012]]<br />
** <br />
* October<br />
**[[QA/StaffMeetings/QA-Staff-10-24-2012|QA-Staff-10-24-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-17-2012|QA-Staff-10-17-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-10-2012|QA-Staff-10-10-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-03-2012|QA-Staff-10-03-2012]]<br />
* September<br />
**[[QA/StaffMeetings/QA-Staff-09-19-2012|QA-Staff-09-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-09-12-2012|QA-Staff-09-12-2012]]<br />
* August<br />
**[[QA/StaffMeetings/QA-Staff-08-29-2012|QA-Staff-08-29-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-22-2012|QA-Staff-08-22-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-15-2012|QA-Staff-08-15-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-08-2012|QA-Staff-08-08-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-01-2012|QA-Staff-08-01-2012]]<br />
<br />
* July<br />
**[[QA/StaffMeetings/QA-Staff-07-25-2012|QA-Staff-07-25-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-18-2012|QA-Staff-07-18-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-11-2012|QA-Staff-07-11-2012]]<br />
<br />
* June<br />
**[[QA/StaffMeetings/QA-Staff-06-27-2012|QA-Staff-06-27-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-20-2012|QA-Staff-06-20-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-13-2012|QA-Staff-06-13-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-06-2012|QA-Staff-06-06-2012]]<br />
<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-30-2012|QA-Staff-05-30-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-23-2012|QA-Staff-05-23-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-16-2012|QA-Staff-05-16-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-09-2012|QA-Staff-05-09-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-02-2012|QA-Staff-05-02-2012]]<br />
* April<br />
** [[QA/StaffMeetings/QA-Staff-04-25-2012|QA-Staff-04-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-18-2012|QA-Staff-04-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-11-2012|QA-Staff-04-11-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-04-2012|QA-Staff-04-04-2012]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-28-2012|QA-Staff-03-28-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-21-2012|QA-Staff-03-21-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-14-2012|QA-Staff-03-14-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-07-2012|QA-Staff-03-07-2012]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-29-2012|QA-Staff-02-29-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-22-2012|QA-Staff-02-22-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-15-2012|QA-Staff-02-15-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-08-2012|QA-Staff-02-08-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-01-2012|QA-Staff-02-01-2012]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-25-2012|QA-Staff-01-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-18-2012|QA-Staff-01-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-04-2012|QA-Staff-01-04-2012]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2011 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-07-2011|QA-Staff-12-07-2011]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-09-2011|QA-Staff-11-09-2011]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-12-2011|QA-Staff-10-12-2011]]<br />
* Sept<br />
** [[QA/StaffMeetings/QA-Staff-09-28-2011|QA-Staff-09-28-2011]]<br />
* August<br />
** [[QA/StaffMeetings/QA-Staff-08-03-2011|QA-Staff-08-03-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-17-2011|QA-Staff-08-17-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-31-2011|QA-Staff-08-31-2011]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-06-2011|QA-Staff-07-06-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-07-20-2011|QA-Staff-07-20-2011]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-08-2011|QA-Staff-06-08-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-06-22-2011|QA-Staff-06-22-2011]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-25-2011|QA-Staff-05-25-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-05-11-2011|QA-Staff-05-11-2011]]<br />
* Apr<br />
** [[QA/StaffMeetings/QA-Staff-04-27-2011|QA-Staff-04-27-2011]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-02-2011|QA-Staff-03-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-16-2011|QA-Staff-03-16-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-30-2011|QA-Staff-03-30-2011]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-02-2011|QA-Staff-02-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-02-16-2011|QA-Staff-02-16-2011]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-05-2011|QA-Staff-01-05-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-01-19-2011|QA-Staff-01-19-2011]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2010 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-08-2010|QA-Staff-12-08-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-12-22-2010|QA-Staff-12-22-2010]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-10-2010|QA-Staff-11-10-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-11-24-2010|QA-Staff-11-24-2010]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-13-2010|QA-Staff-10-13-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-10-27-2010|QA-Staff-10-27-2010]]<br />
* Sep<br />
** [[QA/StaffMeetings/QA-Staff-09-01-2010|QA-Staff-09-01-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-09-29-2010|QA-Staff-09-29-2010]]<br />
* Aug<br />
** [[QA/StaffMeetings/QA-Staff-08-04-2010|QA-Staff-08-04-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-08-18-2010|QA-Staff-08-18-2010]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-21-2010|QA-Staff-07-21-2010]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-09-2010|QA-Staff-06-09-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-06-23-2010|QA-Staff-06-23-2010]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-12-2010|QA-Staff-05-12-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-05-26-2010|QA-Staff-05-26-2010]]<br />
* Apr<br />
** [https://intranet.mozilla.org/QA-Staff-04-14-2010 QA-Staff-04-14-2010]<br />
** [[QA/StaffMeetings/QA-Staff-04-28-2010|QA-Staff-04-28-2010]]<br />
* Mar<br />
** [https://intranet.mozilla.org/QA-Staff-03-10-2010 QA-Staff-03-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-17-2010 QA-Staff-03-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-24-2010 QA-Staff-03-24-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-31-2010 QA-Staff-03-31-2010]<br />
* Feb<br />
** [https://intranet.mozilla.org/QA-Staff-02-03-2010 QA-Staff-02-03-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-10-2010 QA-Staff-02-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-17-2010 QA-Staff-02-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-24-2010 QA-Staff-02-24-2010]<br />
|}</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting&diff=1050185QA/Team Meeting2015-01-26T03:53:26Z<p>Ctalbert: </p>
<hr />
<div>Our every 2 week meeting is open to the public. You're welcome to join.<br />
<br />
== Meeting Details ==<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Angel conference room.<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 9245 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 9245 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 9245 (Canada)<br />
# IRC: [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23qa irc://irc.mozilla.org:6697/#qa]<br />
<br />
* Please see below for next meeting date and previous archived meetings<br />
* [[QA/Team_Meeting/QA_Team_Template|Team Meeting Template]]<br />
* [[QA/StaffMeetings/videos| Videos of meetings]]<br />
<createbox><br />
align=left<br />
type=create<br />
preload=QA/Team_Meeting/QA_Team_Template<br />
default={{#time: Y-m-d | wednesday}}<br />
prefix=QA/Team_Meeting/QA_Team_Meeting-<br />
</createbox><br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2015 <br />
|-<br />
|<br />
* February 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-02-04|QA Team Meeting Feb 4]]<br />
* January 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-21|QA Team Meeting Jan 21]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-14|QA Team Meeting Jan 14]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-07|QA Team Meeting Jan 7]]<br />
|}<br />
<br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2014 <br />
|-<br />
|<br />
* December 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-17|QA Team Meeting Dec 17]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-10|QA Team Meeting Dec 10]]<br />
* November 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-26|QA Team Meeting Nov 26]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-19|QA Team Meeting Nov 19]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-12|QA Team Meeting Nov 12]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-05|QA Team Meeting Nov 5]]<br />
* October 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-29|QA Team Meeting Oct 29]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-22|QA Team Meeting Oct 22]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-15|QA Team Meeting Oct 15]]<br />
** QA Team Meeting Oct 08 - CANCELED<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-01|QA Team Meeting Oct 01]]<br />
*September 2014<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-24 | QA Team Meeting Sept 24]]<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-17 | QA Team Meeting Sept 17]]<br />
**[[QA/Team_Meeting/QA-Team-2014-09-10 | QA Team Meeting Sept 10]]<br />
**[[QA/Team_Meeting/QA-Team-09-03-2014 | QA Team Meeting Sept 3]]<br />
*August 2014<br />
**[[QA/StaffMeetings/QA-Staff-08-27-2014|QA-Staff-08-27-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-20-2014|QA-Staff-08-20-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-13-2014|QA-Staff-08-13-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-06-2014|QA-Staff-08-06-2014]]<br />
*July 2014<br />
** Meeting on July 30 was canceled due to QA Work Week<br />
**[[QA/StaffMeetings/QA-Staff-07-23-2014|QA-Staff-07-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-16-2014|QA-Staff-07-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-09-2014|QA-Staff-07-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-02-2014|QA-Staff-07-02-2014]]<br />
*June 2014<br />
**[[QA/StaffMeetings/QA-Staff-06-25-2014|QA-Staff-06-25-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-18-2014|QA-Staff-06-18-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-11-2014|QA-Staff-06-11-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-04-2014|QA-Staff-06-04-2014]]<br />
*May 2014<br />
**[[QA/StaffMeetings/QA-Staff-05-28-2014|QA-Staff-05-28-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-21-2014|QA-Staff-05-21-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-14-2014|QA-Staff-05-14-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-07-2014|QA-Staff-05-07-2014]]<br />
*April 2014<br />
**[[QA/StaffMeetings/QA-Staff-04-30-2014|QA-Staff-04-30-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-23-2014|QA-Staff-04-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-16-2014|QA-Staff-04-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-09-2014|QA-Staff-04-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-02-2014|QA-Staff-04-02-2014]]<br />
*March 2014<br />
**[[QA/StaffMeetings/QA-Staff-03-26-2014|QA-Staff-03-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-19-2014|QA-Staff-03-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-12-2014|QA-Staff-03-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-05-2014|QA-Staff-03-05-2014]]<br />
*February 2014<br />
**[[QA/StaffMeetings/QA-Staff-02-26-2014|QA-Staff-02-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-19-2014|QA-Staff-02-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-12-2014|QA-Staff-02-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-05-2014|QA-Staff-02-05-2014]]<br />
*January 2014<br />
**[[QA/StaffMeetings/QA-Staff-01-29-2014|QA-Staff-01-29-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-22-2014|QA-Staff-01-22-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-15-2014|QA-Staff-01-15-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-08-2014|QA-Staff-01-08-2014]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2013<br />
|-<br />
|<br />
*December<br />
**[[QA/StaffMeetings/QA-Staff-12-18-2013|QA-Staff-12-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-11-2013|QA-Staff-12-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-04-2013|QA-Staff-12-04-2013]]<br />
*November<br />
**[[QA/StaffMeetings/QA-Staff-11-27-2013|QA-Staff-11-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-20-2013|QA-Staff-11-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-13-2013|QA-Staff-11-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-06-2013|QA-Staff-11-06-2013]]<br />
*October<br />
**[[QA/StaffMeetings/QA-Staff-10-30-2013|QA-Staff-10-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-23-2013|QA-Staff-10-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-16-2013|QA-Staff-10-16-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-09-2013|QA-Staff-10-09-2013]]<br />
*Sept<br />
**[[QA/StaffMeetings/QA-Staff-09-25-2013|QA-Staff-09-25-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-18-2013|QA-Staff-09-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-11-2013|QA-Staff-09-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-04-2013|QA-Staff-09-04-2013]]<br />
*August 2013<br />
**[[QA/StaffMeetings/QA-Staff-08-28-2013|QA-Staff-08-28-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-21-2013|QA-Staff-08-21-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-14-2013|QA-Staff-08-14-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-07-2013|QA-Staff-08-07-2013]]<br />
*July 2013<br />
**[[QA/StaffMeetings/QA-Staff-07-31-2013|QA-Staff-07-31-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-24-2013|QA-Staff-07-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-17-2013|QA-Staff-07-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-10-2013|QA-Staff-07-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-03-2013|QA-Staff-07-03-2013]]<br />
*June 2013<br />
**[[QA/StaffMeetings/QA-Staff-06-26-2013|QA-Staff-06-26-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-19-2013|QA-Staff-06-19-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-12-2013|QA-Staff-06-12-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-05-2013|QA-Staff-06-05-2013]]<br />
*May 2013<br />
**[[QA/StaffMeetings/QA-Staff-05-29-2013|QA-Staff-05-29-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-22-2013|QA-Staff-05-22-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-15-2013|QA-Staff-05-15-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-08-2013|QA-Staff-05-08-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-01-2013|QA-Staff-05-01-2013]]<br />
*April 2013<br />
**[[QA/StaffMeetings/QA-Staff-04-24-2013|QA-Staff-04-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-17-2013|QA-Staff-04-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-10-2013|QA-Staff-04-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-03-2013|QA-Staff-04-03-2013]]<br />
* March 2013<br />
**[[QA/StaffMeetings/QA-Staff-03-27-2013|QA-Staff-03-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-20-2013|QA-Staff-03-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-13-2013|QA-Staff-03-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-06-2013|QA-Staff-03-06-2013]]<br />
* Febuary 2013<br />
**[[QA/StaffMeetings/QA-Staff-02-27-2013|QA-Staff-02-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-20-2013|QA-Staff-02-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-13-2013|QA-Staff-02-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-06-2013|QA-Staff-02-06-2013]]<br />
* January 2013<br />
**[[QA/StaffMeetings/QA-Staff-01-30-2013|QA-Staff-01-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-23-2013|QA-Staff-01-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-16-2013|QA-Staff-01-16-2013]]<br />
|}<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2012<br />
|-<br />
|<br />
* December 2012<br />
**[[QA/StaffMeetings/QA-Staff-12-19-2012|QA-Staff-12-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-12-2012|QA-Staff-12-12-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-05-2012|QA-Staff-12-05-2012]]<br />
* November<br />
**[[QA/StaffMeetings/QA-Staff-11-28-2012|QA-Staff-11-28-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-21-2012|QA-Staff-11-21-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-14-2012|QA-Staff-11-14-2012]]<br />
** <br />
* October<br />
**[[QA/StaffMeetings/QA-Staff-10-24-2012|QA-Staff-10-24-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-17-2012|QA-Staff-10-17-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-10-2012|QA-Staff-10-10-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-03-2012|QA-Staff-10-03-2012]]<br />
* September<br />
**[[QA/StaffMeetings/QA-Staff-09-19-2012|QA-Staff-09-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-09-12-2012|QA-Staff-09-12-2012]]<br />
* August<br />
**[[QA/StaffMeetings/QA-Staff-08-29-2012|QA-Staff-08-29-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-22-2012|QA-Staff-08-22-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-15-2012|QA-Staff-08-15-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-08-2012|QA-Staff-08-08-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-01-2012|QA-Staff-08-01-2012]]<br />
<br />
* July<br />
**[[QA/StaffMeetings/QA-Staff-07-25-2012|QA-Staff-07-25-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-18-2012|QA-Staff-07-18-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-11-2012|QA-Staff-07-11-2012]]<br />
<br />
* June<br />
**[[QA/StaffMeetings/QA-Staff-06-27-2012|QA-Staff-06-27-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-20-2012|QA-Staff-06-20-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-13-2012|QA-Staff-06-13-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-06-2012|QA-Staff-06-06-2012]]<br />
<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-30-2012|QA-Staff-05-30-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-23-2012|QA-Staff-05-23-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-16-2012|QA-Staff-05-16-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-09-2012|QA-Staff-05-09-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-02-2012|QA-Staff-05-02-2012]]<br />
* April<br />
** [[QA/StaffMeetings/QA-Staff-04-25-2012|QA-Staff-04-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-18-2012|QA-Staff-04-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-11-2012|QA-Staff-04-11-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-04-2012|QA-Staff-04-04-2012]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-28-2012|QA-Staff-03-28-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-21-2012|QA-Staff-03-21-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-14-2012|QA-Staff-03-14-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-07-2012|QA-Staff-03-07-2012]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-29-2012|QA-Staff-02-29-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-22-2012|QA-Staff-02-22-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-15-2012|QA-Staff-02-15-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-08-2012|QA-Staff-02-08-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-01-2012|QA-Staff-02-01-2012]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-25-2012|QA-Staff-01-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-18-2012|QA-Staff-01-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-04-2012|QA-Staff-01-04-2012]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2011 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-07-2011|QA-Staff-12-07-2011]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-09-2011|QA-Staff-11-09-2011]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-12-2011|QA-Staff-10-12-2011]]<br />
* Sept<br />
** [[QA/StaffMeetings/QA-Staff-09-28-2011|QA-Staff-09-28-2011]]<br />
* August<br />
** [[QA/StaffMeetings/QA-Staff-08-03-2011|QA-Staff-08-03-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-17-2011|QA-Staff-08-17-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-31-2011|QA-Staff-08-31-2011]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-06-2011|QA-Staff-07-06-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-07-20-2011|QA-Staff-07-20-2011]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-08-2011|QA-Staff-06-08-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-06-22-2011|QA-Staff-06-22-2011]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-25-2011|QA-Staff-05-25-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-05-11-2011|QA-Staff-05-11-2011]]<br />
* Apr<br />
** [[QA/StaffMeetings/QA-Staff-04-27-2011|QA-Staff-04-27-2011]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-02-2011|QA-Staff-03-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-16-2011|QA-Staff-03-16-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-30-2011|QA-Staff-03-30-2011]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-02-2011|QA-Staff-02-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-02-16-2011|QA-Staff-02-16-2011]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-05-2011|QA-Staff-01-05-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-01-19-2011|QA-Staff-01-19-2011]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2010 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-08-2010|QA-Staff-12-08-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-12-22-2010|QA-Staff-12-22-2010]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-10-2010|QA-Staff-11-10-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-11-24-2010|QA-Staff-11-24-2010]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-13-2010|QA-Staff-10-13-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-10-27-2010|QA-Staff-10-27-2010]]<br />
* Sep<br />
** [[QA/StaffMeetings/QA-Staff-09-01-2010|QA-Staff-09-01-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-09-29-2010|QA-Staff-09-29-2010]]<br />
* Aug<br />
** [[QA/StaffMeetings/QA-Staff-08-04-2010|QA-Staff-08-04-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-08-18-2010|QA-Staff-08-18-2010]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-21-2010|QA-Staff-07-21-2010]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-09-2010|QA-Staff-06-09-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-06-23-2010|QA-Staff-06-23-2010]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-12-2010|QA-Staff-05-12-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-05-26-2010|QA-Staff-05-26-2010]]<br />
* Apr<br />
** [https://intranet.mozilla.org/QA-Staff-04-14-2010 QA-Staff-04-14-2010]<br />
** [[QA/StaffMeetings/QA-Staff-04-28-2010|QA-Staff-04-28-2010]]<br />
* Mar<br />
** [https://intranet.mozilla.org/QA-Staff-03-10-2010 QA-Staff-03-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-17-2010 QA-Staff-03-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-24-2010 QA-Staff-03-24-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-31-2010 QA-Staff-03-31-2010]<br />
* Feb<br />
** [https://intranet.mozilla.org/QA-Staff-02-03-2010 QA-Staff-02-03-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-10-2010 QA-Staff-02-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-17-2010 QA-Staff-02-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-24-2010 QA-Staff-02-24-2010]<br />
|}</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2015-02-04&diff=1050184QA/Team Meeting/QA Team Meeting-2015-02-042015-01-26T03:52:36Z<p>Ctalbert: Created page with "= Mozilla QA Meeting Feb 4 2015 = # Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA # # Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIk..."</p>
<hr />
<div>= Mozilla QA Meeting Feb 4 2015 =<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
<br />
== Actions From Last Week ==<br />
<br />
== Deadlines and Schedules ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
=== Other Notable Dates/Events (Read Only) ===<br />
*<br />
<br />
== Discussion & Updates for Team ==<br />
* <small>''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''</small><br />
* Note the new format, review the list of lightningtalks<br />
* Review Goals quickly<br />
<br />
== Lightning Talk ==<br />
* <small>''[[QA/Team_Meeting/Lightning Talk List|Lightning talk list]]''</small><br />
<br />
== Contributors ==<br />
=== New Contributor Spotlight ===<br />
These are new contributors, if you see them around, say hello<br />
*<br />
<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO (Read Only) ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/Lightning_Talk_List&diff=1050181QA/Team Meeting/Lightning Talk List2015-01-26T03:50:49Z<p>Ctalbert: Created page with "This is the list of assignees for Lighting talks during the QA meeting. Keep in mind that you have FOUR minutes total. That's not very long. It does not need to be a demo, it..."</p>
<hr />
<div>This is the list of assignees for Lighting talks during the QA meeting. Keep in mind that you have FOUR minutes total. That's not very long. It does not need to be a demo, it does not need to have slides, though both are welcome. If you have those, be sure they are ready to go, because the time it takes to set up will count against you.<br />
<br />
* Feb 4, 2015: Stephend Topic: <br />
* Feb 18, 2015: Ctalbert Topic:<br />
* Mar 4, 2015: Lizzard Topic:<br />
* Mar 18, 2015: Kairo Topic:<br />
* Apr 1, 2015: Kjozwiak Topic:<br />
* Apr 15, 2015: Aaronmt Topic:<br />
* Apr 29, 2015: Mwobensmith Topic:<br />
* May 13, 2015: Kthiessen Topic:<br />
* May 27, 2015: Marcia Topic:<br />
* Jun 10, 2015: Davehunt Topic:<br />
* Jun 24, 2015: Sydpolk Topic:<br />
* Jul 8, 2015: Mschifer Topic:<br />
* Jul 22, 2015: Juanb Topic:<br />
* Aug 5, 2015: Mbrandt Topic:<br />
* Aug 19, 2015: Pragmatic Topic:<br />
* Sept 2, 2015: Maja Topic:<br />
* Sept 16, 2015: Kraj Topic:<br />
* Sept 30, 2015: Ashughes Topic:<br />
* Oct 14, 2015: Kbrosnan Topic:<br />
* Oct 28, 2015: Pdehaan Topic:<br />
* Nov 11, 2015: Bsilverberg Topic:<br />
* Nov 25, 2015: Rbillings Topic:<br />
* Dec 9, 2015: Jrgm Topic:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Template&diff=1050170QA/Team Meeting/QA Team Template2015-01-26T03:34:17Z<p>Ctalbert: /* Lightning Talk */</p>
<hr />
<div>= Mozilla QA Meeting TODO: INSERT DATE AND TIME OF MTG HERE =<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
<br />
== Actions From Last Week ==<br />
<br />
== Deadlines and Schedules ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
=== Other Notable Dates/Events (Read Only) ===<br />
*<br />
<br />
== Discussion & Updates for Team ==<br />
* <small>''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''</small><br />
<br />
== Lightning Talk ==<br />
* <small>''[[QA/Team_Meeting/Lightning Talk List|Lightning talk list]]''</small><br />
<br />
== Contributors ==<br />
=== New Contributor Spotlight ===<br />
These are new contributors, if you see them around, say hello<br />
*<br />
<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO (Read Only) ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Template&diff=1050169QA/Team Meeting/QA Team Template2015-01-26T03:33:40Z<p>Ctalbert: </p>
<hr />
<div>= Mozilla QA Meeting TODO: INSERT DATE AND TIME OF MTG HERE =<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 99456 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 99456 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 99456 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
<br />
== Actions From Last Week ==<br />
<br />
== Deadlines and Schedules ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
=== Other Notable Dates/Events (Read Only) ===<br />
*<br />
<br />
== Discussion & Updates for Team ==<br />
* <small>''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''</small><br />
<br />
== Lightning Talk ==<br />
* <small>''[[QA/Team_Meeting/Lightning_Talk_List|Lightning talk list]]''</small><br />
<br />
== Contributors ==<br />
=== New Contributor Spotlight ===<br />
These are new contributors, if you see them around, say hello<br />
*<br />
<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO (Read Only) ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting&diff=1050163QA/Team Meeting2015-01-26T03:22:36Z<p>Ctalbert: </p>
<hr />
<div>Our every 2 week meeting is open to the public. You're welcome to join.<br />
<br />
== Meeting Details ==<br />
# Every other Weds @ 1:30p Pacific Time - Mozilla HQ, Angel conference room.<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=0HHQN7SSNIkAxuJq04fq7uZk6J8<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 9245 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 9245 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 9245 (Canada)<br />
# IRC: [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23qa irc://irc.mozilla.org:6697/#qa]<br />
<br />
* Please see below for next meeting date and previous archived meetings<br />
* [[QA/Team_Meeting/QA_Team_Template|Team Meeting Template]]<br />
* [[QA/StaffMeetings/videos| Videos of meetings]]<br />
<createbox><br />
align=left<br />
type=create<br />
preload=QA/Team_Meeting/QA_Team_Template<br />
default={{#time: Y-m-d | wednesday}}<br />
prefix=QA/Team_Meeting/QA_Team_Meeting-<br />
</createbox><br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2015 <br />
|-<br />
|<br />
* January 2015<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-21|QA Team Meeting Jan 21]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-14|QA Team Meeting Jan 14]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2015-01-07|QA Team Meeting Jan 7]]<br />
|}<br />
<br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2014 <br />
|-<br />
|<br />
* December 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-17|QA Team Meeting Dec 17]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-12-10|QA Team Meeting Dec 10]]<br />
* November 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-26|QA Team Meeting Nov 26]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-19|QA Team Meeting Nov 19]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-12|QA Team Meeting Nov 12]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-11-05|QA Team Meeting Nov 5]]<br />
* October 2014<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-29|QA Team Meeting Oct 29]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-22|QA Team Meeting Oct 22]]<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-15|QA Team Meeting Oct 15]]<br />
** QA Team Meeting Oct 08 - CANCELED<br />
** [[QA/Team_Meeting/QA_Team_Meeting-2014-10-01|QA Team Meeting Oct 01]]<br />
*September 2014<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-24 | QA Team Meeting Sept 24]]<br />
**[[QA/Team_Meeting/QA_Team_Meeting-2014-09-17 | QA Team Meeting Sept 17]]<br />
**[[QA/Team_Meeting/QA-Team-2014-09-10 | QA Team Meeting Sept 10]]<br />
**[[QA/Team_Meeting/QA-Team-09-03-2014 | QA Team Meeting Sept 3]]<br />
*August 2014<br />
**[[QA/StaffMeetings/QA-Staff-08-27-2014|QA-Staff-08-27-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-20-2014|QA-Staff-08-20-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-13-2014|QA-Staff-08-13-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-08-06-2014|QA-Staff-08-06-2014]]<br />
*July 2014<br />
** Meeting on July 30 was canceled due to QA Work Week<br />
**[[QA/StaffMeetings/QA-Staff-07-23-2014|QA-Staff-07-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-16-2014|QA-Staff-07-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-09-2014|QA-Staff-07-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-07-02-2014|QA-Staff-07-02-2014]]<br />
*June 2014<br />
**[[QA/StaffMeetings/QA-Staff-06-25-2014|QA-Staff-06-25-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-18-2014|QA-Staff-06-18-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-11-2014|QA-Staff-06-11-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-06-04-2014|QA-Staff-06-04-2014]]<br />
*May 2014<br />
**[[QA/StaffMeetings/QA-Staff-05-28-2014|QA-Staff-05-28-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-21-2014|QA-Staff-05-21-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-14-2014|QA-Staff-05-14-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-05-07-2014|QA-Staff-05-07-2014]]<br />
*April 2014<br />
**[[QA/StaffMeetings/QA-Staff-04-30-2014|QA-Staff-04-30-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-23-2014|QA-Staff-04-23-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-16-2014|QA-Staff-04-16-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-09-2014|QA-Staff-04-09-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-04-02-2014|QA-Staff-04-02-2014]]<br />
*March 2014<br />
**[[QA/StaffMeetings/QA-Staff-03-26-2014|QA-Staff-03-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-19-2014|QA-Staff-03-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-12-2014|QA-Staff-03-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-03-05-2014|QA-Staff-03-05-2014]]<br />
*February 2014<br />
**[[QA/StaffMeetings/QA-Staff-02-26-2014|QA-Staff-02-26-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-19-2014|QA-Staff-02-19-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-12-2014|QA-Staff-02-12-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-02-05-2014|QA-Staff-02-05-2014]]<br />
*January 2014<br />
**[[QA/StaffMeetings/QA-Staff-01-29-2014|QA-Staff-01-29-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-22-2014|QA-Staff-01-22-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-15-2014|QA-Staff-01-15-2014]]<br />
**[[QA/StaffMeetings/QA-Staff-01-08-2014|QA-Staff-01-08-2014]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2013<br />
|-<br />
|<br />
*December<br />
**[[QA/StaffMeetings/QA-Staff-12-18-2013|QA-Staff-12-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-11-2013|QA-Staff-12-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-12-04-2013|QA-Staff-12-04-2013]]<br />
*November<br />
**[[QA/StaffMeetings/QA-Staff-11-27-2013|QA-Staff-11-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-20-2013|QA-Staff-11-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-13-2013|QA-Staff-11-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-11-06-2013|QA-Staff-11-06-2013]]<br />
*October<br />
**[[QA/StaffMeetings/QA-Staff-10-30-2013|QA-Staff-10-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-23-2013|QA-Staff-10-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-16-2013|QA-Staff-10-16-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-10-09-2013|QA-Staff-10-09-2013]]<br />
*Sept<br />
**[[QA/StaffMeetings/QA-Staff-09-25-2013|QA-Staff-09-25-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-18-2013|QA-Staff-09-18-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-11-2013|QA-Staff-09-11-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-09-04-2013|QA-Staff-09-04-2013]]<br />
*August 2013<br />
**[[QA/StaffMeetings/QA-Staff-08-28-2013|QA-Staff-08-28-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-21-2013|QA-Staff-08-21-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-14-2013|QA-Staff-08-14-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-08-07-2013|QA-Staff-08-07-2013]]<br />
*July 2013<br />
**[[QA/StaffMeetings/QA-Staff-07-31-2013|QA-Staff-07-31-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-24-2013|QA-Staff-07-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-17-2013|QA-Staff-07-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-10-2013|QA-Staff-07-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-07-03-2013|QA-Staff-07-03-2013]]<br />
*June 2013<br />
**[[QA/StaffMeetings/QA-Staff-06-26-2013|QA-Staff-06-26-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-19-2013|QA-Staff-06-19-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-12-2013|QA-Staff-06-12-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-06-05-2013|QA-Staff-06-05-2013]]<br />
*May 2013<br />
**[[QA/StaffMeetings/QA-Staff-05-29-2013|QA-Staff-05-29-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-22-2013|QA-Staff-05-22-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-15-2013|QA-Staff-05-15-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-08-2013|QA-Staff-05-08-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-05-01-2013|QA-Staff-05-01-2013]]<br />
*April 2013<br />
**[[QA/StaffMeetings/QA-Staff-04-24-2013|QA-Staff-04-24-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-17-2013|QA-Staff-04-17-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-10-2013|QA-Staff-04-10-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-04-03-2013|QA-Staff-04-03-2013]]<br />
* March 2013<br />
**[[QA/StaffMeetings/QA-Staff-03-27-2013|QA-Staff-03-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-20-2013|QA-Staff-03-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-13-2013|QA-Staff-03-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-03-06-2013|QA-Staff-03-06-2013]]<br />
* Febuary 2013<br />
**[[QA/StaffMeetings/QA-Staff-02-27-2013|QA-Staff-02-27-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-20-2013|QA-Staff-02-20-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-13-2013|QA-Staff-02-13-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-02-06-2013|QA-Staff-02-06-2013]]<br />
* January 2013<br />
**[[QA/StaffMeetings/QA-Staff-01-30-2013|QA-Staff-01-30-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-23-2013|QA-Staff-01-23-2013]]<br />
**[[QA/StaffMeetings/QA-Staff-01-16-2013|QA-Staff-01-16-2013]]<br />
|}<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2012<br />
|-<br />
|<br />
* December 2012<br />
**[[QA/StaffMeetings/QA-Staff-12-19-2012|QA-Staff-12-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-12-2012|QA-Staff-12-12-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-12-05-2012|QA-Staff-12-05-2012]]<br />
* November<br />
**[[QA/StaffMeetings/QA-Staff-11-28-2012|QA-Staff-11-28-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-21-2012|QA-Staff-11-21-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-11-14-2012|QA-Staff-11-14-2012]]<br />
** <br />
* October<br />
**[[QA/StaffMeetings/QA-Staff-10-24-2012|QA-Staff-10-24-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-17-2012|QA-Staff-10-17-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-10-2012|QA-Staff-10-10-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-10-03-2012|QA-Staff-10-03-2012]]<br />
* September<br />
**[[QA/StaffMeetings/QA-Staff-09-19-2012|QA-Staff-09-19-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-09-12-2012|QA-Staff-09-12-2012]]<br />
* August<br />
**[[QA/StaffMeetings/QA-Staff-08-29-2012|QA-Staff-08-29-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-22-2012|QA-Staff-08-22-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-15-2012|QA-Staff-08-15-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-08-2012|QA-Staff-08-08-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-08-01-2012|QA-Staff-08-01-2012]]<br />
<br />
* July<br />
**[[QA/StaffMeetings/QA-Staff-07-25-2012|QA-Staff-07-25-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-18-2012|QA-Staff-07-18-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-07-11-2012|QA-Staff-07-11-2012]]<br />
<br />
* June<br />
**[[QA/StaffMeetings/QA-Staff-06-27-2012|QA-Staff-06-27-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-20-2012|QA-Staff-06-20-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-13-2012|QA-Staff-06-13-2012]]<br />
**[[QA/StaffMeetings/QA-Staff-06-06-2012|QA-Staff-06-06-2012]]<br />
<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-30-2012|QA-Staff-05-30-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-23-2012|QA-Staff-05-23-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-16-2012|QA-Staff-05-16-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-09-2012|QA-Staff-05-09-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-05-02-2012|QA-Staff-05-02-2012]]<br />
* April<br />
** [[QA/StaffMeetings/QA-Staff-04-25-2012|QA-Staff-04-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-18-2012|QA-Staff-04-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-11-2012|QA-Staff-04-11-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-04-04-2012|QA-Staff-04-04-2012]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-28-2012|QA-Staff-03-28-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-21-2012|QA-Staff-03-21-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-14-2012|QA-Staff-03-14-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-03-07-2012|QA-Staff-03-07-2012]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-29-2012|QA-Staff-02-29-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-22-2012|QA-Staff-02-22-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-15-2012|QA-Staff-02-15-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-08-2012|QA-Staff-02-08-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-02-01-2012|QA-Staff-02-01-2012]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-25-2012|QA-Staff-01-25-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-18-2012|QA-Staff-01-18-2012]]<br />
** [[QA/StaffMeetings/QA-Staff-01-04-2012|QA-Staff-01-04-2012]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2011 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-07-2011|QA-Staff-12-07-2011]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-09-2011|QA-Staff-11-09-2011]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-12-2011|QA-Staff-10-12-2011]]<br />
* Sept<br />
** [[QA/StaffMeetings/QA-Staff-09-28-2011|QA-Staff-09-28-2011]]<br />
* August<br />
** [[QA/StaffMeetings/QA-Staff-08-03-2011|QA-Staff-08-03-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-17-2011|QA-Staff-08-17-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-08-31-2011|QA-Staff-08-31-2011]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-06-2011|QA-Staff-07-06-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-07-20-2011|QA-Staff-07-20-2011]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-08-2011|QA-Staff-06-08-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-06-22-2011|QA-Staff-06-22-2011]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-25-2011|QA-Staff-05-25-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-05-11-2011|QA-Staff-05-11-2011]]<br />
* Apr<br />
** [[QA/StaffMeetings/QA-Staff-04-27-2011|QA-Staff-04-27-2011]]<br />
* Mar<br />
** [[QA/StaffMeetings/QA-Staff-03-02-2011|QA-Staff-03-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-16-2011|QA-Staff-03-16-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-03-30-2011|QA-Staff-03-30-2011]]<br />
* Feb<br />
** [[QA/StaffMeetings/QA-Staff-02-02-2011|QA-Staff-02-02-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-02-16-2011|QA-Staff-02-16-2011]]<br />
* Jan<br />
** [[QA/StaffMeetings/QA-Staff-01-05-2011|QA-Staff-01-05-2011]]<br />
** [[QA/StaffMeetings/QA-Staff-01-19-2011|QA-Staff-01-19-2011]]<br />
|}<br />
<br />
{| class="wikitable collapsible autocollapse" style="width: 100%"<br />
! 2010 <br />
|-<br />
|<br />
* Dec<br />
** [[QA/StaffMeetings/QA-Staff-12-08-2010|QA-Staff-12-08-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-12-22-2010|QA-Staff-12-22-2010]]<br />
* Nov<br />
** [[QA/StaffMeetings/QA-Staff-11-10-2010|QA-Staff-11-10-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-11-24-2010|QA-Staff-11-24-2010]]<br />
* Oct<br />
** [[QA/StaffMeetings/QA-Staff-10-13-2010|QA-Staff-10-13-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-10-27-2010|QA-Staff-10-27-2010]]<br />
* Sep<br />
** [[QA/StaffMeetings/QA-Staff-09-01-2010|QA-Staff-09-01-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-09-29-2010|QA-Staff-09-29-2010]]<br />
* Aug<br />
** [[QA/StaffMeetings/QA-Staff-08-04-2010|QA-Staff-08-04-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-08-18-2010|QA-Staff-08-18-2010]]<br />
* July<br />
** [[QA/StaffMeetings/QA-Staff-07-21-2010|QA-Staff-07-21-2010]]<br />
* June<br />
** [[QA/StaffMeetings/QA-Staff-06-09-2010|QA-Staff-06-09-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-06-23-2010|QA-Staff-06-23-2010]]<br />
* May<br />
** [[QA/StaffMeetings/QA-Staff-05-12-2010|QA-Staff-05-12-2010]]<br />
** [[QA/StaffMeetings/QA-Staff-05-26-2010|QA-Staff-05-26-2010]]<br />
* Apr<br />
** [https://intranet.mozilla.org/QA-Staff-04-14-2010 QA-Staff-04-14-2010]<br />
** [[QA/StaffMeetings/QA-Staff-04-28-2010|QA-Staff-04-28-2010]]<br />
* Mar<br />
** [https://intranet.mozilla.org/QA-Staff-03-10-2010 QA-Staff-03-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-17-2010 QA-Staff-03-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-24-2010 QA-Staff-03-24-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-03-31-2010 QA-Staff-03-31-2010]<br />
* Feb<br />
** [https://intranet.mozilla.org/QA-Staff-02-03-2010 QA-Staff-02-03-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-10-2010 QA-Staff-02-10-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-17-2010 QA-Staff-02-17-2010]<br />
** [https://intranet.mozilla.org/QA-Staff-02-24-2010 QA-Staff-02-24-2010]<br />
|}</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2015-01-21&diff=1049400QA/Team Meeting/QA Team Meeting-2015-01-212015-01-21T14:24:48Z<p>Ctalbert: </p>
<hr />
<div>= Mozilla QA Meeting Jan 21 2015 =<br />
# Every Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=nL4PESn1IaVh<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 9245 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 9245 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 9245 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
== Notices and Schedule ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
* Media MSE changes still poised for 36 for Youtube - help watch videos on youtube if you're on windows and report results<br />
<br />
== Actions From Last Week ==<br />
* Review meeting (Karl, Matt B, Clint, Stephen)<br />
<br />
== Discussion Zone ==<br />
* ''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''<br />
* Changes proposed to this meeting: https://groups.google.com/forum/#!topic/mozilla.dev.quality/agd1ZkvGkl0<br />
<br />
== QA Show and Tell ==<br />
<br />
== Updates, Milestones, Deadlines (2min each call to action)==<br />
* Samples:<br />
** A call to action: {{action|<Information>|<Contact Person>}}<br />
** A notice of information (will be read only so make it complete, but don't write a novel): {{fyi|<Information>}}<br />
<br />
== Upcoming Events ==<br />
<br />
== Community ==<br />
<br />
== Contributor Spotlight ==<br />
These are new contributors, if you see them around, say hello<br />
*<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2015-01-21&diff=1049396QA/Team Meeting/QA Team Meeting-2015-01-212015-01-21T14:22:17Z<p>Ctalbert: Created page with "= Mozilla QA Meeting Jan 21 2015 = # Every Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA # # Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=nL4PESn1IaVh #..."</p>
<hr />
<div>= Mozilla QA Meeting Jan 21 2015 =<br />
# Every Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA<br />
#<br />
# Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=nL4PESn1IaVh<br />
# Phone: +1 650 903 0800 or 650-215-1282 x92 Conf# 9245 (US/INTL)<br />
# +1 800 707 2533 (pin 369) Conf# 9245 (US Toll Free)<br />
# +1 416 848 3114 x92 Conf# 9245 (Canada)<br />
# IRC: irc://irc.mozilla.org:6697/#qa<br />
<br />
<small>Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template</small><br />
== Notices and Schedule ==<br />
{| class="wikitable" style="color:green; background-color:#ffffcc;" cellpadding="10" padding="5"<br />
|-<br />
|colspan="2"|<big>Next Merge:</big> '''{{FIREFOX_MERGE_DATE}}'''<br />
|colspan="2"|<big>Next Release:</big> '''{{FIREFOX_SHIP_DATE}}'''<br />
|-<br />
!colspan="4" style="color:black;"|Trains<br />
|-<br />
|Central: {{CENTRAL_VERSION}} <br />
|Aurora: {{AURORA_VERSION}} <br />
|Beta: {{BETA_VERSION}} <br />
|Release: {{RELEASE_VERSION}}<br />
|-<br />
|}<br />
* Media MSE changes still poised for 36 for Youtube - help watch videos on youtube if you're on windows and report results<br />
<br />
== Actions From Last Week ==<br />
* Review meeting (Karl, Matt B, Clint, Stephen)<br />
<br />
== Discussion Zone ==<br />
* ''Pick a notetaker for our [https://etherpad.mozilla.org/qa-team-meeting-notes notepad]''<br />
* Changes proposed to this meeting: https://groups.google.com/forum/#!topic/mozilla.dev.quality/agd1ZkvGkl0<br />
<br />
== QA Show and Tell ==<br />
<br />
== Updates, Milestones, Deadlines (2min each call to action)==<br />
* Samples:<br />
** A call to action: {{action|<Information>|<Contact Person>}}<br />
** A notice of information (will be read only so make it complete, but don't write a novel): {{fyi|<Information>}}<br />
<br />
== Upcoming Events ==<br />
<br />
== Community ==<br />
<br />
== Contributor Spotlight ==<br />
These are new contributors, if you see them around, say hello<br />
*<br />
=== Contributor Honor Roll ===<br />
For those that went above and beyond this week, we salute you here.<br />
*<br />
<br />
== Quarter Goals ==<br />
* Monthly Review: https://wiki.mozilla.org/QA/Goals/2015q1<br />
** In-meeting review first meeting of every month<br />
<br />
== Action Items and notes from the meeting ==<br />
* Please '''bold''' action items. <br />
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad]<br />
<br />
== Travel / PTO ==<br />
* [https://www.google.com/calendar/embed?src=j41a8ne525ml0heaipg0idb6is%40group.calendar.google.com&ctz=America/Los_Angeles QA PTO Calendar] (Google)<br />
<br />
== For Further Information ==<br />
All of these meetings listed below are open to the public. You're encouraged to join whichever interest you. Each meeting has an archive where the notes are captured, so in order to get a sense of what is happening on a specific project, feel free to either join or review the meeting notes archive. And if you have questions, you can always find us on IRC. <br />
<br />
=== [https://wiki.mozilla.org/QA/Firefox Firefox QE] ===<br />
* Who we are: Individuals focused on Firefox Desktop, Firefox Android, and Gecko Platform Quality<br />
* Meetings held weekly on [http://arewemeetingyet.com/Los%20Angeles/2014-08-20/08:30/w/Firefox%20QE Wednesdays at 8:30AM Pacific Time]<br />
* To Join:<br />
** Vidyo: <br />
*** Room: QA-Desktop<br />
*** [https://v.mozilla.com/flex.html?roomdirect.html&key=RU7dVysDFakY Vidyo Guest URL]<br />
** Phone (use any of these): <br />
*** '''1-650-903-0800''' or '''1-650-215-1282''' US/INTL<br />
*** '''1-800-707-2533''' Toll Free US/Skype<br />
*** If using a 650 number, use Extension: '''92'''<br />
*** If using the 1-800 number, use PIN: '''369'''<br />
*** Conference Number: '''99779'''<br />
* [https://wiki.mozilla.org/QA/Firefox/TeamMeetings Meeting Notes Archive]<br />
* Next Agenda: No published agenda<br />
<br />
=== [https://wiki.mozilla.org/B2G/QA Firefox OS] ===<br />
* Who we are: Individuals focused on Firefox OS Quality<br />
* Meetings held weekly on [http://arewemeetingyet.com/Los%20Angeles/2014-08-20/17:00/w/Firefox%20OS%20QA Wednesdays at 5:00PM Pacific Time]<br />
* To Join:<br />
** Vidyo<br />
*** Room: QA Vidyo Room (same as this meeting)<br />
*** [https://v.mozilla.com/flex.html?roomdirect.html&key=nL4PESn1IaVh Guest URL] <br />
** Phone (use any of these):<br />
*** '''1-650-903-0800''' or '''1-650-215-1282''' US/INTL<br />
*** '''1-800-707-2533''' Toll Free US/Skype<br />
*** If using a 650 number, use Extension: '''92'''<br />
*** If using the 1-800 number, use PIN: '''369'''<br />
*** Conference Number: '''9245'''<br />
** IRC: irc://irc.mozilla.org:6697/#fxosqa<br />
* [https://wiki.mozilla.org/B2G/QA/Meetings Meeting Notes Archive]<br />
* [https://mozqa.etherpad.mozilla.org/b2g-qa-roundtable Next Agenda]<br />
<br />
=== [https://wiki.mozilla.org/QA/Services Services QA] ===<br />
* Who we are: Individuals focused on Quality of the services that power features of all products<br />
* Meetings held weekly on [http://arewemeetingyet.com/Los%20Angeles/2014-08-25/15:30/w/Services%20QA Mondays at 3:30PM Pacfic Time]<br />
* To Join:<br />
** Vidyo<br />
*** Room: QA (same as this meeting)<br />
*** [https://v.mozilla.com/flex.html?roomdirect.html&key=nL4PESn1IaVh Guest URL] <br />
** Phone (use any of these):<br />
*** '''1-650-903-0800''' or '''1-650-215-1282''' US/INTL<br />
*** '''1-800-707-2533''' Toll Free US/Skype<br />
*** If using a 650 number, use Extension: '''92'''<br />
*** If using the 1-800 number, use PIN: '''369'''<br />
*** Conference Number: '''9245'''<br />
** IRC: irc://irc.mozilla.org:6697/#qa<br />
* Meeting Notes Archive: No archive<br />
* Next Agenda: No published agenda<br />
<br />
=== [https://wiki.mozilla.org/QA/Execution/Web_Testing Web QA] ===<br />
* Who we are: Individuals focused on maintaining the Quality of Mozilla's web properties, and improving the core QA websites we all use.<br />
* Meetings held weekly on [http://arewemeetingyet.com/Los%20Angeles/2014-08-21/09:00/w/Web%20QA Thursdays at 9:00AM Pacific Time]<br />
* To Join:<br />
** Vidyo<br />
*** Room: Stephen Donner<br />
*** [https://v.mozilla.com/flex.html?roomdirect.html&key=ZAlDIwL9AJcf Guest URL]<br />
** Phone (use any of these):<br />
*** '''1-650-903-0800''' or '''1-650-215-1282''' US/INTL<br />
*** '''1-800-707-2533''' Toll Free US/Skype<br />
*** If using a 650 number, use Extension: '''92'''<br />
*** If using the 1-800 number, use PIN: '''369'''<br />
*** Conference Number: '''9303'''<br />
** IRC: irc://irc.mozilla.org:6697/#mozwebqa<br />
* [https://wiki.mozilla.org/QA/Execution/Web_Testing/Meeting_Notes Meeting Notes Archive]<br />
* Next Agenda: No published Agenda<br />
<br />
=== Platform QA ===<br />
* Who we are: Individuals focused on investigating and increasing Quality in the Gecko platform that underlies all our products<br />
* Meetings <br />
** This team runs in two week sprints, so the meetings are a combination of planning and standups. First time contributors to this team are encouraged to attend the next sprint planning meeting.<br />
** [http://arewemeetingyet.com/Los%20Angeles/2014-09-02/13:00/b/Sprint%20Planning%20for%20Platform%20QA Sprint Planning every other Tuesdays 1:00PM-2:00PM Pacific]<br />
** Sprint Standups [http://arewemeetingyet.com/Los%20Angeles/2014-08-26/13:00/b/Sprint%20Planning%20for%20Platform%20QA every other Tuesday 1:30PM-2:00PM Pacific] PDT and [http://arewemeetingyet.com/Los%20Angeles/2014-08-29/10:00/w/Sprint%20Standup%20for%20Platform%20QA every Friday 10:00AM-10:30AM Pacific]<br />
* To Join:<br />
** Vidyo<br />
*** Room: Platform-QA<br />
*** Guest URL: <TBD><br />
** Phone:<br />
*** '''1-650-903-0800''' or '''1-650-215-1282''' US/INTL<br />
*** '''1-800-707-2533''' Toll Free US/Skype<br />
*** If using a 650 number, use Extension: '''92'''<br />
*** If using the 1-800 number, use PIN: '''369'''<br />
*** Conference Number: '''98613'''<br />
** IRC: irc://irc.mozilla.org:6697/#qa<br />
* Instead of agenda, follow along on the [https://www.pivotaltracker.com/s/projects/1139894 Pivotal Tracker board]<br />
<br />
=== Community Champions ===<br />
* Who we are: Individuals from every aspect of QA focused on improving all aspects of our community involvement<br />
* Meetings [http://arewemeetingyet.com/Los%20Angeles/2014-08-22/13:00/b/Community%20Champions held every other Friday 1:00PM Pacific]<br />
* To Join:<br />
** Vidyo<br />
*** Room: Marcia Knous<br />
*** [https://v.mozilla.com/flex.html?roomdirect.html&key=7ZfgNjQBGgTa Guest URL]<br />
** Phone:<br />
*** '''1-650-903-0800''' or '''1-650-215-1282''' US/INTL<br />
*** '''1-800-707-2533''' Toll Free US/Skype<br />
*** If using a 650 number, use Extension: '''92'''<br />
*** If using the 1-800 number, use PIN: '''369'''<br />
*** Conference Number: '''9214'''<br />
* [https://wiki.mozilla.org/QA/Community_Champions#Meeting_Notes Meeting Notes Archive]<br />
* Next Agenda: No Published Agenda<br />
<br />
=== Crashkill ===<br />
* Who we are: Individuals focused on monitoring and ensuring that reported crashes in our products get addressed<br />
* Meetings [http://arewemeetingyet.com/Los%20Angeles/2014-08-25/10:00/w/Crashkill held weekly on Mondays at 10:00AM Pacific]<br />
* To Join:<br />
** Vidyo<br />
*** Room: Stability<br />
*** [https://v.mozilla.com/flex.html?roomdirect.html&key=Rrxgrs93WsX2 Guest URL]<br />
** Phone:<br />
*** '''1-650-903-0800''' or '''1-650-215-1282''' US/INTL<br />
*** '''1-800-707-2533''' Toll Free US/Skype<br />
*** If using a 650 number, use Extension: '''92'''<br />
*** If using the 1-800 number, use PIN: '''369'''<br />
*** Conference Number: '''98200'''<br />
** IRC: irc://irc.mozilla.org:6697/#crashkill<br />
* [https://wiki.mozilla.org/CrashKill#Meeting_notes Meeting Notes Archive]<br />
* Next Agenda: No Published Agenda<br />
<br />
===Kittens===<br />
Kitten, fox, or other cute animal gif of the week:</div>Ctalberthttps://wiki.mozilla.org/index.php?title=Platform/2015-Q1-Goals&diff=1047662Platform/2015-Q1-Goals2015-01-14T04:58:29Z<p>Ctalbert: /* QA */</p>
<hr />
<div>== Platform ==<br />
== General Goals (by Team) ==<br />
=== GFX ===<br />
=== Layout ===<br />
<br />
=== Media ===<br />
<br />
=== DOM ===<br />
<br />
=== JS ===<br />
<br />
=== Accessibility ===<br />
<br />
=== Perf ===<br />
<br />
=== Networking ===<br />
<br />
=== Mobile ===<br />
<br />
=== A*Team ===<br />
<br />
See [https://trello.com/b/3BjXQCEp/a-team-projects our Trello board] for the complete list.<br />
<br />
'''Highlights''':<br />
* Support the conversion of mozmill Firefox update tests to Marionette<br />
* MozReview: add autolander integration with Tryserver<br />
* MozReview: improve Bugzilla integration<br />
* Bugzilla: implement an alternate bug view<br />
* Perfherder: develop a UI inside Treeherder that can be used to inspect Talos performance data<br />
* Treeherder: create the ability to distinguish between Tier 1 and Tier 2 jobs<br />
* Android: develop Android 4.4 emulator images that can be used for test jobs<br />
* Prototype a "big data" project that logs detailed information about tests that can be used to normalize test chunks, identify tests that never fail versus those that do, and be of source of other metrics in the future<br />
* Resolve issues that block us from releasing Marionette 1.0<br />
<br />
=== QA ===<br />
<br />
See [[QA/Goals/2015q1|our wiki]] for the complete list<br />
<br />
''' Highlights:'''<br />
* Automate kick off of update testing, automating entire release process save manual spot-checks<br />
* Begin process for converting automated update and l10n tests to marionette in preparation for e10s (all P1 tests converted)<br />
* Help relieve user headaches from Flash powered content<br />
* Bring quality teams closer to engineering and increase technical acumen in high priority areas<br />
* Create set of risk factor metrics to be used across codebase to identify potential areas of relative risk<br />
* Make security testing automation more robust and more streamlined<br />
* Complete payments automation coverage<br />
* Create a community taskforce to do QA on a specific pilot project<br />
<br />
=== Web Engineering ===<br />
==== crash-stats ====<br />
<br />
==== DXR ====<br />
<br />
==== SUMO ====<br />
* Finish BuddyUp Phase 1<br />
* Finish Questions Forum redesign<br />
* Contributor Metrics Dashboard<br />
* Pay down Technical Debt<br />
** Upgrade to the latest Django (1.7, most likely)<br />
** Get SUMO on Python 2.7<br />
** Switch to py.test<br />
** Stop using test_utils<br />
<br />
==== Input ====<br />
* Upgrade to Django 1.7<br />
* Upgrade other libraries to appropriate versions now that Input is on Python 2.7<br />
* 12-factor app work ([[Firefox/Input/12 Factor App|12 Factor App]])<br />
* Prepare for AWS move (set up a stage environment in AWS?)<br />
* 1-5 gradient ratings ([[Firefox/Input/Gradient Sentiment|Gradient Sentiment]])<br />
* Thank you page overhaul ([[Firefox/Input/Thank you page|Thank you page]]) (via OPW intern)<br />
<br />
=== Release Engineering / Release Operations / Developer Services ===<br />
* Virtualize Windows builders and get builds running in the cloud<br />
* Drive some of our builds out of taskcluster<br />
* Schedule reduced test load (depends on A-team)<br />
* Ship production quality 1.0 of MozReview and Autoland<br />
* Scope and begin implementation of release automation changes with the goal to cut release time in half.<br />
* Support OS X 10.10 builds with minimum additional cost<br />
<br />
=== Security & Privacy ===<br />
see [https://wiki.mozilla.org/SecurityEngineering/2015/Q1Goals Security Engineering 2015, Q1 Goals]<br />
<br />
=== Firefox and Platform Security ===<br />
<br />
=== Games Program ===<br />
<br />
=== Program/Project Management ===</div>Ctalberthttps://wiki.mozilla.org/index.php?title=Platform/2015-Q1-Goals&diff=1047661Platform/2015-Q1-Goals2015-01-14T04:57:16Z<p>Ctalbert: /* QA */</p>
<hr />
<div>== Platform ==<br />
== General Goals (by Team) ==<br />
=== GFX ===<br />
=== Layout ===<br />
<br />
=== Media ===<br />
<br />
=== DOM ===<br />
<br />
=== JS ===<br />
<br />
=== Accessibility ===<br />
<br />
=== Perf ===<br />
<br />
=== Networking ===<br />
<br />
=== Mobile ===<br />
<br />
=== A*Team ===<br />
<br />
See [https://trello.com/b/3BjXQCEp/a-team-projects our Trello board] for the complete list.<br />
<br />
'''Highlights''':<br />
* Support the conversion of mozmill Firefox update tests to Marionette<br />
* MozReview: add autolander integration with Tryserver<br />
* MozReview: improve Bugzilla integration<br />
* Bugzilla: implement an alternate bug view<br />
* Perfherder: develop a UI inside Treeherder that can be used to inspect Talos performance data<br />
* Treeherder: create the ability to distinguish between Tier 1 and Tier 2 jobs<br />
* Android: develop Android 4.4 emulator images that can be used for test jobs<br />
* Prototype a "big data" project that logs detailed information about tests that can be used to normalize test chunks, identify tests that never fail versus those that do, and be of source of other metrics in the future<br />
* Resolve issues that block us from releasing Marionette 1.0<br />
<br />
=== QA ===<br />
<br />
See [[QA/Goals/2015q1|our wiki]] for the complete list<br />
<br />
''' Highlights:'''<br />
* {{ok|Automate kick off of update testing, automating entire release process save manual spot-checks}}<br />
* {{ok|Begin process for converting automated update and l10n tests to marionette in preparation for e10s (all P1 tests converted)}}<br />
* {{ok|Help relieve user headaches from Flash powered content}}<br />
* {{ok|Bring quality teams closer to engineering and increase technical acumen in high priority areas}}<br />
* {{ok|Create set of risk factor metrics to be used across codebase to identify potential areas of relative risk}}<br />
* {{ok|Make security testing automation more robust and more streamlined}}<br />
* {{ok|Complete payments automation coverage}}<br />
* {{ok|Create a community taskforce to do QA on a specific pilot project}}<br />
<br />
=== Web Engineering ===<br />
==== crash-stats ====<br />
<br />
==== DXR ====<br />
<br />
==== SUMO ====<br />
* Finish BuddyUp Phase 1<br />
* Finish Questions Forum redesign<br />
* Contributor Metrics Dashboard<br />
* Pay down Technical Debt<br />
** Upgrade to the latest Django (1.7, most likely)<br />
** Get SUMO on Python 2.7<br />
** Switch to py.test<br />
** Stop using test_utils<br />
<br />
==== Input ====<br />
* Upgrade to Django 1.7<br />
* Upgrade other libraries to appropriate versions now that Input is on Python 2.7<br />
* 12-factor app work ([[Firefox/Input/12 Factor App|12 Factor App]])<br />
* Prepare for AWS move (set up a stage environment in AWS?)<br />
* 1-5 gradient ratings ([[Firefox/Input/Gradient Sentiment|Gradient Sentiment]])<br />
* Thank you page overhaul ([[Firefox/Input/Thank you page|Thank you page]]) (via OPW intern)<br />
<br />
=== Release Engineering / Release Operations / Developer Services ===<br />
* Virtualize Windows builders and get builds running in the cloud<br />
* Drive some of our builds out of taskcluster<br />
* Schedule reduced test load (depends on A-team)<br />
* Ship production quality 1.0 of MozReview and Autoland<br />
* Scope and begin implementation of release automation changes with the goal to cut release time in half.<br />
* Support OS X 10.10 builds with minimum additional cost<br />
<br />
=== Security & Privacy ===<br />
see [https://wiki.mozilla.org/SecurityEngineering/2015/Q1Goals Security Engineering 2015, Q1 Goals]<br />
<br />
=== Firefox and Platform Security ===<br />
<br />
=== Games Program ===<br />
<br />
=== Program/Project Management ===</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1047659QA/Goals/2015q12015-01-14T04:40:29Z<p>Ctalbert: /* Milestones this Quarter */</p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Deliberate<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Impact<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Mozfactor<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Overall Quality<br />
| style="font-weight: bold; background: #DDD; width: 48%" | Rationale<br />
|-<br />
| Firefox 35<br />
| Jan 12 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Firefox 36<br />
| Feb 23 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Spring Release Planning<br />
| Ongoing<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| New Embedded Team Sprints<br />
| ongoing<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Marionette Training and test conversion<br />
| Feb 1 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "Green-light" test framework in preparation for E10s}}<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{ok|<small>[lizzard, juanb]</small> - Establish baselines for automated test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}} <br />
* {{ok|<small>[lizzard, juanb]</small> - Improve the automated test coverage for E10s enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve addon compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{ok|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{ok|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing web platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
* {{ok|<small>[aaronmt, kbrosnan]</small> - Slim down the per release smoketest by at least 25%}}<br />
* {{ok|<small>[kbrosnan]</small> - Investigate using marionette/firefox greenlight on Fennec, create a plan and prioritized set of targets for the marionette team}}<br />
* {{ok|<small>[aaronmt]</small> - Fix or discontinue appthwak automation}}<br />
<br />
== Web QA ==<br />
* {{prev|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{prev|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg?]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 Make Web QA's Jenkins public}}<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>Identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)]}} <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require addon signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on youtube by supporting the media team in shipping MSE on youtube for windows vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1047656QA/Goals/2015q12015-01-14T04:37:04Z<p>Ctalbert: /* Milestones this Quarter */</p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Deliberate<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Impact<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Mozfactor<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Overall Quality<br />
| style="font-weight: bold; background: #DDD; width: 48%" | Rationale<br />
|-<br />
| Firefox 35<br />
| Jan 12 2015<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "Green-light" test framework in preparation for E10s}}<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{ok|<small>[lizzard, juanb]</small> - Establish baselines for automated test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}} <br />
* {{ok|<small>[lizzard, juanb]</small> - Improve the automated test coverage for E10s enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve addon compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{ok|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{ok|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing web platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
* {{ok|<small>[aaronmt, kbrosnan]</small> - Slim down the per release smoketest by at least 25%}}<br />
* {{ok|<small>[kbrosnan]</small> - Investigate using marionette/firefox greenlight on Fennec, create a plan and prioritized set of targets for the marionette team}}<br />
* {{ok|<small>[aaronmt]</small> - Fix or discontinue appthwak automation}}<br />
<br />
== Web QA ==<br />
* {{prev|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{prev|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg?]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 Make Web QA's Jenkins public}}<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>Identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)]}} <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require addon signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on youtube by supporting the media team in shipping MSE on youtube for windows vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1047655QA/Goals/2015q12015-01-14T04:36:33Z<p>Ctalbert: /* Milestones this Quarter */</p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Deliberate<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Impact<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Mozfactor<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Overall Quality<br />
| style="font-weight: bold; background: #DDD; width: 48%" | Rationale<br />
|-<br />
| Firefox 35<br />
| Jan 12 2015<br />
|<br />
|<br />
|<br />
|<br />
|<br />
}<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "Green-light" test framework in preparation for E10s}}<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{ok|<small>[lizzard, juanb]</small> - Establish baselines for automated test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}} <br />
* {{ok|<small>[lizzard, juanb]</small> - Improve the automated test coverage for E10s enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve addon compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{ok|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{ok|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing web platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
* {{ok|<small>[aaronmt, kbrosnan]</small> - Slim down the per release smoketest by at least 25%}}<br />
* {{ok|<small>[kbrosnan]</small> - Investigate using marionette/firefox greenlight on Fennec, create a plan and prioritized set of targets for the marionette team}}<br />
* {{ok|<small>[aaronmt]</small> - Fix or discontinue appthwak automation}}<br />
<br />
== Web QA ==<br />
* {{prev|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{prev|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg?]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 Make Web QA's Jenkins public}}<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>Identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)]}} <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require addon signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on youtube by supporting the media team in shipping MSE on youtube for windows vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1047653QA/Goals/2015q12015-01-14T04:26:47Z<p>Ctalbert: /* Web QA */</p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Delight<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Dependability<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Security & Privacy<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Performance<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Overall Score<br />
| style="font-weight: bold; background: #DDD; width: 40%" | Rationale<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "Green-light" test framework in preparation for E10s}}<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{ok|<small>[lizzard, juanb]</small> - Establish baselines for automated test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}} <br />
* {{ok|<small>[lizzard, juanb]</small> - Improve the automated test coverage for E10s enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve addon compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{ok|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{ok|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing web platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
* {{ok|<small>[aaronmt, kbrosnan]</small> - Slim down the per release smoketest by at least 25%}}<br />
* {{ok|<small>[kbrosnan]</small> - Investigate using marionette/firefox greenlight on Fennec, create a plan and prioritized set of targets for the marionette team}}<br />
* {{ok|<small>[aaronmt]</small> - Fix or discontinue appthwak automation}}<br />
<br />
== Web QA ==<br />
* {{prev|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{prev|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg?]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 Make Web QA's Jenkins public}}<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>Identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap after the API work (API to be covered by camd)]}} <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require addon signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on youtube by supporting the media team in shipping MSE on youtube for windows vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1047652QA/Goals/2015q12015-01-14T04:25:43Z<p>Ctalbert: /* Fennec */</p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Delight<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Dependability<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Security & Privacy<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Performance<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Overall Score<br />
| style="font-weight: bold; background: #DDD; width: 40%" | Rationale<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "Green-light" test framework in preparation for E10s}}<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{ok|<small>[lizzard, juanb]</small> - Establish baselines for automated test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}} <br />
* {{ok|<small>[lizzard, juanb]</small> - Improve the automated test coverage for E10s enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve addon compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{ok|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{ok|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing web platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
* {{ok|<small>[aaronmt, kbrosnan]</small> - Slim down the per release smoketest by at least 25%}}<br />
* {{ok|<small>[kbrosnan]</small> - Investigate using marionette/firefox greenlight on Fennec, create a plan and prioritized set of targets for the marionette team}}<br />
* {{ok|<small>[aaronmt]</small> - Fix or discontinue appthwak automation}}<br />
<br />
== Web QA ==<br />
* {{prev|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{prev|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg?]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 Make Web QA's Jenkins public}}<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap]}}: <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require addon signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on youtube by supporting the media team in shipping MSE on youtube for windows vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1047651QA/Goals/2015q12015-01-14T04:25:10Z<p>Ctalbert: /* Fennec */</p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Delight<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Dependability<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Security & Privacy<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Performance<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Overall Score<br />
| style="font-weight: bold; background: #DDD; width: 40%" | Rationale<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "Green-light" test framework in preparation for E10s}}<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{ok|<small>[lizzard, juanb]</small> - Establish baselines for automated test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}} <br />
* {{ok|<small>[lizzard, juanb]</small> - Improve the automated test coverage for E10s enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve addon compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{ok|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{ok|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing web platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
{{ok|<small>[aaronmt, kbrosnan] - Slim down the per release smoketest by at least 25%}}<br />
{{ok|<small>[kbrosnan] - Investigate using marionette/firefox greenlight on Fennec, create a plan and prioritized set of targets for the marionette team}}<br />
{{ok|<small>[aaronmt]</small> - Fix or discontinue appthwak automation}}<br />
<br />
== Web QA ==<br />
* {{prev|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{prev|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg?]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 Make Web QA's Jenkins public}}<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap]}}: <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require addon signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on youtube by supporting the media team in shipping MSE on youtube for windows vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2015q1&diff=1047650QA/Goals/2015q12015-01-14T04:24:36Z<p>Ctalbert: </p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Delight<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Dependability<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Security & Privacy<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Performance<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Overall Score<br />
| style="font-weight: bold; background: #DDD; width: 40%" | Rationale<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| .<br />
| .<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
== General Quality ==<br />
* {{ok|<small>[whimboo, with help: ctalbert, kairo, releng]</small> Automate [https://github.com/mozilla/mozmill-ci/issues/535 kicking off update tests] so that the release process is automated end to end except manual spot checks}}<br />
* {{ok|<small>[stephend, joint with a*team]</small> Coordinate training and prioritize efforts to convert P1 tests from Mozmill to the Marionette "Green-light" test framework in preparation for E10s}}<br />
* {{ok|<small>[whimboo, a*team]</small> Get Marionette Green-light tests running in the QA CI system for at least Nightly tests}}<br />
* {{ok|<small>[mschifer]</small> Create and monitor a set of risk factor metrics to understand risks in areas where we have no embedded QA}}<br />
* {{ok|<small>[kairo]</small> Create a better concept for tracking crash-stats that more reflects the actual risk and severity of the crashes involved (than the current top 10 list)}}<br />
<br />
== Firefox ==<br />
=== E10s ===<br />
* {{ok|<small>[lizzard, juanb]</small> - Establish baselines for automated test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}} <br />
* {{ok|<small>[lizzard, juanb]</small> - Improve the automated test coverage for E10s enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}<br />
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve addon compatibility testing for e10s}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa<br />
<br />
=== DOM ===<br />
* {{ok|<small>[tracy]</small> - Document best practices for triage and test writing for DOM issues to pave the way for community involvement}}<br />
* {{ok|<small>[ashughes]</small> - Establish baseline metrics for specification coverage, test stability, and other DOM quality metrics and track them throughout Q1}}<br />
* {{ok|<small>[tracy, ashughes]</small> - Create several new automated tests/get existing web platform tests working to support the Picture tag and ServiceWorkers specifications}}<br />
** milestones/deliverables: https://etherpad.mozilla.org/qa-dom-strategy<br />
<br />
=== Security/Privacy ===<br />
* {{ok|<small>[mwobensmith]</small> - Set up AWS instance to run large TLS regression test}}<br />
* {{ok|<small>[mwobensmith]</small> - Create a fast running subset of the larger TLS test and automate to run per-release (i.e. pre-beta)}}<br />
* {{ok|<small>[kjoziwak]</small> - Monitor and create telemetry probes to gather data to help serve as an early warning system for risky changes}}<br />
<br />
=== Fennec ===<br />
{{ok|<small>[aaronmt, kbrosnan] - Slim down the per release smoketest by at least 25%}}<br />
{{ok|<small>[kbrosnan] - Investigate using marionette/firefox greenlight on Fennec, create a plan and prioritized set of targets for the marionette team}}<br />
{{ok|<small>[aaronmt] - Fix or discontinue appthwak automation}}<br />
<br />
{{ok|<small><br />
== Web QA ==<br />
* {{prev|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** {{prev|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{ok|<small>[bsilverberg?]</small> - QA Metrics Dashboard - collate metrics on a page of links as new metrics are proven to be useful}}<br />
* {{ok|<small>[davehunt]</small> - bug 1112555 Make Web QA's Jenkins public}}<br />
* {{ok|<small>[mbrandt/bsilverberg] - </small>identify and deliver on the highest [https://www.pivotaltracker.com/n/projects/280483 priority/biggest pain-points of MozTrap]}}: <br />
* {{prev|<small>[krupa]</small> - Have automation coverage for Payments including in-app payments}}<br />
** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
* {{ok|<small>[krupa]</small> - Coordinate and drive quality efforts to prepare for AMO to require addon signing}}<br />
<br />
== Platform QA ==<br />
* {{ok|<small>[Marcia, Syd]</small> Eliminate Flash issues on youtube by supporting the media team in shipping MSE on youtube for windows vista and higher through manual and automated testing}}<br />
<br />
== Community ==<br />
* [marcia] Build community effort to support the Buddy Up project<br />
* [ashughes] Help create at least three small, focused test-day events that focus on helping contributors be more effective</div>Ctalberthttps://wiki.mozilla.org/index.php?title=QA/Goals/2014q4&diff=1045609QA/Goals/2014q42015-01-07T21:59:39Z<p>Ctalbert: </p>
<hr />
<div>= Milestones this Quarter =<br />
This is the list of milestones this quarter. The table below is used to judge how our efforts shaped each axis of quality in the final release. We'll fill this in after the quarter completes.<br />
{| class="fullwidth-table" border="1"<br />
|-<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Milestone<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Date<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Delight<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Dependability<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Security & Privacy<br />
| style="font-weight: bold; background: #DDD; width: 8%" | Performance<br />
| style="font-weight: bold; background: #DDD; width: 10%" | Overall Score<br />
| style="font-weight: bold; background: #DDD; width: 40%" | Rationale<br />
|-<br />
| Firefox Ten Year<br />
| Nov 9<br />
| B<br />
| B<br />
| A<br />
| A<br />
| B<br />
| Fast turnaround release - tough to get done in time, lots of web production work as well. Very lucky this worked out well given 33.<br />
|-<br />
| Firefox 33<br />
| Oct 13<br />
| F<br />
| C<br />
| A<br />
| A<br />
| C<br />
| Black screen issues, omtc issues resulted in obscurring other issues<br />
|-<br />
| Firefox 34<br />
| Nov 25<br />
| B<br />
| B-<br />
| A<br />
| A<br />
| B-<br />
| Search could have gone better - we caught issues but no time to fix before it went live. Kamil did an amazing job getting a pre-look at it and getting many of the issues filed. Secrecy of the search release really impacted our ability to be effective. Loop uplifts and coordination issues with server side proved difficult and fraught with issues, worked out in the end. Lots of confusion in user community about slow roll-out of the loop feature - need better documentation going forward<br />
|-<br />
| PDX Work week<br />
| Dec 1 - 6<br />
| n/a<br />
| n/a<br />
| n/a<br />
| n/a<br />
| n/a<br />
| n/a<br />
|-<br />
| Marketplace shift to FxAccounts<br />
| Oct 31<br />
| A<br />
| A<br />
| A<br />
| A<br />
| A<br />
| Moved from persona to FxAccounts. Went quite smoothly even though there was a lot of churn. Automation in place helped a lot as well.<br />
|-<br />
| Marketplace ship on Tarako Device in new location<br />
| Oct - Nov<br />
| A<br />
| A<br />
| A<br />
| A<br />
| A<br />
| Shipped without a ton of work on our side, which surprised us. We thought this would be bigger than it turned out to be.<br />
|-<br />
| QMO Update<br />
| Nov 20?<br />
| A<br />
| A<br />
| A<br />
| A<br />
| A<br />
| Went really well. Docs on MDN was a lot of work, but was led well.<br />
|-<br />
| MozFest<br />
| Oct 24-26<br />
| B<br />
| A<br />
| A<br />
| A<br />
| A<br />
| QA standpoint - gave out 1000 phones, and sent people back into the communities. Would have been nice to have had sessions around that to teach people to be effective contributing with the phones.<br />
|-<br />
| Firefox OS 2.1<br />
| Nov 30<br />
| A<br />
| A<br />
| A<br />
| A<br />
| A<br />
| Best quality release of Fx OS to date (from partner feedback)<br />
|-<br />
| Loop Ship<br />
| Nov 25<br />
| B<br />
| B<br />
| A<br />
| A<br />
| B<br />
| Largest issues were mostly out of our control - miscommunications happening between the various groups. We were all hearing different things and spending considerable amount of time to track down source of truth and adjust strategies appropriately. Volume of uplifts was high but we dealt with it, had a separate branch which helped quite a bit.<br />
|-<br />
| E10S on by default in nightly<br />
| Nov 9<br />
| A<br />
| A<br />
| A<br />
| A<br />
| A little difficulty with some nighlty users - being able to flip it off easily in the pref pane was a huge win. The pain we encountered was good and made the e10s system more resilient going forward.<br />
|-<br />
|}<br />
<br />
== General Quality ==<br />
* {{done|Create a centralized site of all dashboard/project information from all quality teams (opt in, per team) so that it is easier to understand the impact and effect of on-going quality efforts}}<br />
** {{miss|<small>[ctalbert]</small> Add churn metrics to the dashboard for platform codebase}}<br />
*** NOTE: We have the values for churn, but the metrics team wasn't able to complete the work to combine this with bugzilla data to have a true modelling for when things are going off the rails. [https://docs.google.com/a/mozilla.com/spreadsheets/d/13ApE-wvEnp1aGKoURy0BeyiBYSYNgag-lGfgi4PZnTg/edit#gid=966645904 Churn values are here]<br />
** {{miss|<small>[mschifer]</small> Include SUMO metrics for support requests over time}}<br />
** {{done|<small>[bsilverberg]</small> Identify and produce metrics around the "drop-off rate" of One and Done tasks for tracking}}<br />
** {{done|<small>[ctalbert]</small> Invite services QA to add in relevant, high level dashboards for cross-QA projects (like Loop, FxAccounts etc)}}<br />
* {{done|Deploy a simpler, streamlined version of QMO}}<br />
** {{done|<small>[pragmatic]</small> Consolidate all QA Docs onto MDN and/or Moz Wiki as appropriate}}<br />
** {{done|<small>[aaronmt]</small> Use our social media presences for digital outreach to create a bit of buzz around the QMO deployment measured by an increase in number of first time contributors}}<br />
* {{done|<small>[aaronmt/ashughes]</small> Testdays: Based on feedback gathered in Q3, prioritize and resolve some of the barriers to participation with a goal of developing some contributors engaged outside of these events (ex. active in bugzilla/moztrap/one&done day-to-day).}}<br />
** Hypothesis: if we provide more frequent bite-sized mentorship opportunities through testdays we'll develop more established relationships in other contribution channels<br />
<br />
== Firefox ==<br />
* {{done|<small>[mschifer]</small> Work on doing fewer verifications since they don't seem to be effective, and use the time saved for exploratory testing.}}<br />
** Hypothesis: We will still produce releases just as high quality but will be able to find more interesting bugs sooner in the development cycles.<br />
** Hypothesis: We will be able to use our fledgling churn metrics to guide where and when to do verifications for non-security bugs (all security bugs continue to be verified if possible).<br />
* {{done|<small>[lizzard]</small> Clarify/standardize/improve how we do QA for Firefox through the entire release process. Have a fairly standard wiki template for each Firefox channel that we can use for tracking and for our daily workflow. We can support community better in helping us (and support each other) better if we have a good transparent window into how QA works across each "train"}}<br />
* {{done|<small>[mschifer]</small> Develop a system to measure development pace for SV Automation (similar to FxTeam) so we can establish a historical baseline and begin to measure an increase pace of automated test development}}<br />
<br />
== Web QA ==<br />
* {{miss|<small>[mbrandt and shared with MDN dev]</small> Develop and stand up a JavaScript-based testing infrastructure (proof-of-concept)}} which allows Web development and Web QA to be maximally effective by sharing key points of test infrastructure, visibility, and process/workflow:<br />
** '''Carried this over to Q1 2015, and will post the week of January 4th'''<br />
*** In the interim: https://etherpad.mozilla.org/mbrandt-q4-intern-status<br />
*** There's also a pull request for the Travis-CI integration: https://github.com/mozilla/kuma/pull/2947<br />
** {{done|<small>[MDN]</small> identify, document, and prioritize current testing challenges and needs}}<br />
** {{done|<small>[mbrandt]</small> create the plan (incl. decisions, next steps/action items, owners, dependencies, agreed-upon process/workflow changes, etc.) to best-attempt to address those needs}}<br />
** {{done|<small>[mbrandt]</small> execute against the plan -- according to decided owners -- noting new dependencies, shifts in direction, limitations, etc.}}<br />
** {{miss|<small>[mbrandt]</small> at the end of the quarter, do a writeup (blog post?) covering the progress and any next steps for Q1 2015}}<br />
* {{done|<small>[rbillings]</small> Review current commitments in terms of projects and transition several to community and/or developers until the set of sites is both sustainable and our time spent on them is impactful}}<br />
* {{done|Finalize Marketplace support requirements for Firefox OS}}<br />
** {{done|<small>[krupa]</small> Ensure automation runs on 2.0 using Flame devices set for 319Mb of RAM to simulate Tarako}}<br />
*** Running here: http://jenkins1.qa.scl3.mozilla.com/view/Marketplace/<br />
** {{miss|<small>[krupa]</small> Have automation coverage for Payments including in-app payments}}<br />
*** total scope of work (done vs. remaining) here: [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1015251&hide_resolved=0 bug 1015251]<br />
*** ''NOTE: we took a sizable hit due to having to switch from Persona -> FxAccounts: https://github.com/mozilla/marketplace-tests-gaia/pull/57'''<br />
<br />
== Platform QA ==<br />
* {{miss|<small>[sydpolk/nils]</small> Complete WebRTC connection establishment and connection quality tests by deploying them to the automation created in Q3 and have them reporting to Treeherder}}<br />
** NOTE:The system reports pass/fail but without logs, because we have to be responsible for reserving the space for the logs which was not scoped in this requirement originally. We will return to this and finish it in Q1, post 36 ship.<br />
* {{done|<small>[sydpolk/nils]</small> Start and deliver at least one sprint on a new (non-WebRTC) project - project TBD, likely one of: (gfx hardware discovery, MSE)}}<br />
<br />
== Community ==<br />
* {{done|<small>[ctalbert]</small> Create the long term 2015 plan for community that addresses how we move our contributors from one-time contributors to active and core contributors}}<br />
* {{done|<small>[marcia]</small> Participate in the Mozilla Spaces Bug Squash November 1-2 (London and Paris offices) with the explicit goal of getting more QA ideas and process instilled in Firefox OS contributors}}<br />
* {{done|<small>[marcia]</small> Participate in the Mozilla Festival October 24-26 with the goal of sharing QA best practices around FX OS, and give community the setup they need to make in an impact in the project.}}<br />
* {{done|<small>[bsilverberg]</small> One and Done: Build a metrics dashboard that exposes data on the most completed & most abandoned tasks, identifying contributors who are making an impact}}<br />
* {{miss|<small>[ctalbert, aaronmt, rbillings, ashughes, marcia]</small> Use Community Calls, new testdays, community buddy, etc as a bridge between one and done and the larger community in order to help contributors cross the gap between "doing something in one and done" and being an active contributor.}}<br />
** Hypothesis: if we execute well on these initiatives we'll see a decline in the drop-off rate between 1 task contributors and multiple task contributors and we can use that to see if these efforts are successful.<br />
** <small>ashughes</small> I think this is at risk partly because we defined a KPI without establishing a baseline. Specifically for testdays, we have done well to integrate One & Done to our workflow but I really don't know if it's had a measurable impact.<br />
* {{done|<small>[pragmatic]</small> QMO Re-design: Complete the migration of Docs off QMO to MDN QA Zone. Roll the new design on to the live site.}}</div>Ctalbert