QA/Goals/2014q2: Difference between revisions

 
(40 intermediate revisions by 14 users not shown)
Line 25: Line 25:
| Addition of token server, verifier, migration, fixes, sync 1.5, etc
| Addition of token server, verifier, migration, fixes, sync 1.5, etc
| June 10
| June 10
|
| A
|-
|-
| Svcs/Desktop
| Svcs/Desktop
Line 31: Line 31:
| Early Engagement, Planning, automation and testing
| Early Engagement, Planning, automation and testing
| June 10
| June 10
|
| A
|-
|-
| FxOS/Svcs/Web
| FxOS/Svcs/Web
Line 37: Line 37:
| Early engagement, planning, testing, and automation
| Early engagement, planning, testing, and automation
| June 10
| June 10
|  
| C
 
|-
|-
| FxOS
| FxOS
Line 50: Line 49:
| Get 1.3t through IOT testing
| Get 1.3t through IOT testing
| April 28
| April 28
|  
| B
|-
|-
| FxOS
| FxOS
Line 62: Line 61:
| Engage with 2.0 teams, drive stability on master, early testing
| Engage with 2.0 teams, drive stability on master, early testing
| Ongoing throughout quarter - branch on June 9
| Ongoing throughout quarter - branch on June 9
|  
| B-
|-
|-
| Web
| Web
Line 68: Line 67:
| Establish continuous deployment mechanism for socorro (crash-stats.m.c)
| Establish continuous deployment mechanism for socorro (crash-stats.m.c)
| June 30
| June 30
|
| A
|}
|}


== Internal Goals (By Project) ==
== Internal Goals (By Project) ==
=== Desktop Firefox ===
=== Desktop Firefox ===
* {{risk|Improve Geolocation Testing by ensuring that if geolocation code fails to work the failure will be noticed}} [juanb]
* {{done|Improve Geolocation Testing by ensuring that if geolocation code fails to work the failure will be noticed}} [juanb]
* {{risk|Improve regression testing for gaming technologies by unhiding webGL automated tests, ensuring automated emscripten tests are run daily}} [kamil]
* {{drop|Improve regression testing for gaming technologies by unhiding webGL automated tests, ensuring automated emscripten tests are run daily}} [kamil]
* {{ok|Create necessary test materials and infrastructure for Loop Product to ensure testing can be shared with partners}} [ashughes]
* {{done|Create necessary test materials and infrastructure for Loop Product to ensure testing can be shared with partners}} [ashughes]
* {{ok|Complete and publish metrics from bugs, regressions, root cause analysis, stability, and uplifts}} [lizzard,kairo]
* {{done|Complete and publish metrics from bugs, regressions, root cause analysis, stability, and uplifts}} [lizzard,kairo]


=== Desktop Automation ===
=== Desktop Automation ===
* {{ok|Ensure Mozmill systems are controlled by puppet for all updates on Mac and Linux systems}}
* {{miss|Ensure Mozmill systems are controlled by puppet for all updates on Mac and Linux systems}}
* {{ok|Set up TPS (sync automation) continuous integration}}
** RelOps is not able to spend too much time on us given they have their own goals to finish. So what's left to do is the coverage for Java and Flash, which is blocked on {{bug|1032133}}
* {{ok|Automate specific tests as identified by Desktop team as features needing automation (Aim to automate 90% of requests)}}
* {{done|Set up TPS (sync automation) continuous integration}}
* {{ok|Provide automation training to larger community through 4 automation training events}}
* {{done|Automate specific tests as identified by Desktop team as features needing automation (Aim to automate 90% of requests)}}
* {{ok|Replace one component of Mozmill with the necessary changes to have it using marionette as its engine in the future}}
* {{done|Provide automation training to larger community through 4 automation training events}}
* {{miss|Replace one component of Mozmill with the necessary changes to have it using marionette as its engine in the future}}
** The patch is ready but was blocked on final updates, and the upgrade of wptserve on PyPI. So it will land a couple days late


=== Android Firefox ===
=== Android Firefox ===
Line 92: Line 93:


=== Web QA ===  
=== Web QA ===  
* {{ok|Get Flame devices running in on-device automation within 5% of the same failure rate as the Buri phones}}
* {{done|Get Flame devices running in on-device automation within 5% of the same failure rate as the Buri phones}}
** Tracking [https://bugzilla.mozilla.org/show_bug.cgi?id=999503 bug 999503]
** Tracking [https://bugzilla.mozilla.org/show_bug.cgi?id=999503 bug 999503]
* {{risk|Complete and publish metrics on project health started in Q1}}
* {{miss|Complete and publish metrics on project health started in Q1}}
** We thought Tableau was a given for this quarter (carried over from last), but given the Metrics team's resourcing and priorities, we're doing this in-house
** We thought Tableau was a given for this quarter (carried over from last), but given the Metrics team's resourcing and priorities, we're doing this in-house
*** I think we'll be able to understand what we can and can't use, metrics-wise, from what we're already measuring in Bugzilla
*** I think we'll be able to understand what we can and can't use, metrics-wise, from what we're already measuring in Bugzilla
* {{ok|Expand marketplace payment testing by improving automated regression testing}}
** [https://wiki.mozilla.org/QA/Execution/Web_Testing/B2G/Metrics Partial Metrics from Bugzilla bugs]
** Well in hand - [https://github.com/mozilla/marketplace-tests-gaia/commits/master commits] and [http://selenium.qa.mtv2.mozilla.com:8080/view/Marketplace/job/b2g.hamachi.mozilla-b2g28_v1_3.v1.3.marketplace/ latest results]
* {{done|Expand marketplace payment testing by improving automated regression testing}}
** [https://github.com/mozilla/marketplace-tests-gaia/commits/master commits] and [http://selenium.qa.mtv2.mozilla.com:8080/view/Marketplace/job/b2g.hamachi.mozilla-b2g28_v1_3.v1.3.marketplace/ latest results]
* {{done|Streamline FxOS smoketest running and reporting by unifying manual and automated smoketests}}
* {{done|Streamline FxOS smoketest running and reporting by unifying manual and automated smoketests}}
** The HTML Reporting, the separate smoketest builds, and tinderbox builds have us set up to implement what's left, which is the process piece
** The HTML Reporting, the separate smoketest builds, and tinderbox builds have us set up to implement what's left, which is the process piece
Line 105: Line 107:
* {{done|Streamline FxOS smoketest running and reporting by unifying manual and automated smoketests. }} [jason/marcia]
* {{done|Streamline FxOS smoketest running and reporting by unifying manual and automated smoketests. }} [jason/marcia]
** Plan established with contractors, Flame automation up, starting up on June 5th
** Plan established with contractors, Flame automation up, starting up on June 5th
* {{risk|Build a proof-of-concept dashboard to display smoketest information}} [johan]
* {{done|Build a proof-of-concept dashboard to display smoketest information}} [johan]
* {{risk|Create a plan to engage community testing now that there are contributors armed with devices (tablets and flames)}}[marcia - falls under community goal as well]  
* {{miss|Create a plan to engage community testing now that there are contributors armed with devices (tablets and flames)}}[marcia - falls under community goal as well]  
* {{ok|Complete and publish project metrics identified in Q1}} [geo]
* {{miss|Complete and publish project metrics identified in Q1}} [geo]
** Kicked off, tasks distributed https://etherpad.mozilla.org/fxosqa-metrics-q2
** Kicked off, tasks distributed https://etherpad.mozilla.org/fxosqa-metrics-q2
* {{ok|Optimize team support so that we can use the timezones and different teams to take advantage of our geolocations (passing off QA Urgent to Taipei)}} [tony]
* {{done|Optimize team support so that we can use the timezones and different teams to take advantage of our geolocations}} [tony]
* {{ok|Support efforts to create automated regression testing for graphics on Fx OS}} [no-jun]
** {{done|distribute mainstream support to US (flame), partner device support to TW (dolphin, tarako)}}
** {{done|arranging contract test houses on both sides to collaborate efforts}}
** {{miss|setup flame automation across TW and US for daily support}}
*** TW had a delay of getting flames in stock, and will not have time this quarter to set up an automation rig like the US QA lab.  TW will revisit this in Q3
* {{done|Support efforts to create automated regression testing for graphics on Fx OS}} [no-jun]
** https://wiki.mozilla.org/B2G/QA/Device_Test_Plan/Graphics
* {{done|Unify acceptance criteria with other teams (UX, Product, Dev) within sprints and report on project health at various milestones (1.5 timeframe)}} [jason/tony]
* {{done|Unify acceptance criteria with other teams (UX, Product, Dev) within sprints and report on project health at various milestones (1.5 timeframe)}} [jason/tony]
** See this [https://wiki.mozilla.org/Release_Management/FirefoxOS/Release_Milestones page] for documented acceptance criteria for QA
** See this [https://wiki.mozilla.org/Release_Management/FirefoxOS/Release_Milestones page] for documented acceptance criteria for QA
Line 118: Line 125:
* {{done|Publish project health metrics created in Q1}} - [https://wiki.mozilla.org/QA/Services/FxA_Sync_QoS metrics] [edwong]
* {{done|Publish project health metrics created in Q1}} - [https://wiki.mozilla.org/QA/Services/FxA_Sync_QoS metrics] [edwong]
* {{done|Ensure FxA has regression tests on FxOS by removing 2 barriers to developers}} (Rpapa wrote sample tests for dev to provide both a framework and a template) [rpappa]
* {{done|Ensure FxA has regression tests on FxOS by removing 2 barriers to developers}} (Rpapa wrote sample tests for dev to provide both a framework and a template) [rpappa]
* {{ok|Work with desktop to ensure loop server system is thoroughly covered by test plans}}[pdehaan/jbonacci]
* {{done|Work with desktop to ensure loop server system is thoroughly covered by test plans}}[pdehaan/jbonacci]
* {{miss|Establish a Services [[https://wiki.mozilla.org/QA/Contribute/QA_201#Curriculum_Development.2FPedagogy|QA 101 tiger team of contributors]] and lead them to help ensure Tokenserver, FindMyDevice, Sync 1.5, Simplepush etc are seeing adequate test coverage for the release level of each of those systems}} [kthiessen]
* {{done|Establish a Services QA 101 tiger team of contributors and lead them to help ensure Tokenserver, FindMyDevice, Sync 1.5, Simplepush etc are seeing adequate test coverage for the release level of each of those systems}} [kthiessen]
** {{done|Talk to 6 contributors about Services QA projects they're interested in.}}
** {{done|Talk to 6 contributors about Services QA projects they're interested in.}}
** {{ok|Start curriculum development on [[QA/Contribute/QA_101|QA 101]], as outlined below in the Community goal.  After the curriculum is developed, then in Q3 assemble a team to contribute to these projects.}}
** {{done|Talk to developers on the above project teams to find out where they need help.}}
** {{ok|Have a conversation with a community leader to help co-ordinate the tiger team.}}
** {{done|Have a conversation with a community leader to help co-ordinate the tiger team.}}
* {{ok|OAuth sign in for Marketplace and FMD cross browser automation}} [kthiessen/team]
* {{done|OAuth sign in for Marketplace and FMD cross browser automation}} [kthiessen/team]


=== Platform Quality ===
=== Platform Quality ===
Line 129: Line 136:
* {{done|Create "Sunshine"/"Happy Path" test automation system in mtn view for webRTC}}
* {{done|Create "Sunshine"/"Happy Path" test automation system in mtn view for webRTC}}
* {{done|Analyze intermittent failures in webRTC and attempt 5 plausible solutions, attempting to reduce occurrence rates of all the webRTC intermittent tests by 10%}}
* {{done|Analyze intermittent failures in webRTC and attempt 5 plausible solutions, attempting to reduce occurrence rates of all the webRTC intermittent tests by 10%}}
* {{ok|Increase quality level of webRTC code by expanding covered scenarios being tested (non-virtual systems, TURN, STUN, NATs, integrating with Loop partners, etc)}}
* {{miss|Increase quality level of webRTC code by expanding covered scenarios being tested (non-virtual systems, TURN, STUN, NATs, integrating with Loop partners, etc)}}
* {{ok|Continue expanding prioritized backlog with an eye toward other platform related projects}}
** We outlined the strategy for this. We are just now starting to build this out. Sunny Day environment took longer than expected.
* {{done|Continue expanding prioritized backlog with an eye toward other platform related projects}}


=== Community ===
=== Community ===
*FX OS
*FX OS
** {{ok|Investigate using Mulet as a possible Task in One and Done [marcia]}}
** {{miss|Investigate using Mulet as a possible Task in One and Done [marcia]}}
** {{ok|Identify a set of QA contributors that should be the first ones to get the Flame and or Flatfish devices [marcia]}}
*** Never had time to start this project.
** {{ok|Create getting Started Documents on QMO in Firefox OS section [marcia]}}
** {{done|Identify a set of QA contributors that should be the first ones to get the Flame and or Flatfish devices [marcia]}}
*** Flame devices are not done, will carry over.
** {{done|Create getting Started Documents on QMO in Firefox OS section [marcia]}}
*** Tony created a create first step for FX OS, so I am considering this goal complete. We will continue refining.
** {{done|Conduct one Test Event this quarter for either the Flame device or Flatfish device [marcia]}}
** {{done|Conduct one Test Event this quarter for either the Flame device or Flatfish device [marcia]}}
* Tools
* Tools
** {{ok|Provide historical and ongoing data for QA community contributions to the Baloo project and define what reports we need back from them}} [lizzard] {{Bug|990667}}
** {{done|Provide historical and ongoing data for QA community contributions to the Baloo project and define what reports we need back from them}} [lizzard] {{Bug|990667}}{{Bug|1017201}}
** {{done|Generate Requirements Document for version 2 of One and Done}} - [lizzard/rbillings](Tracking info here: https://wiki.mozilla.org/QA/OneandDone)
** {{done|Generate Requirements Document for version 2 of One and Done}} - [lizzard/rbillings](Tracking info here: https://wiki.mozilla.org/QA/OneandDone)
* Recognition
* Recognition
** {{done|Create a Badges working group}} [rbillings]
** {{done|Create a Badges working group}} [rbillings]
** {{ok|Produce one specific piece of QA swag to deploy to contributors}} [marcia]
** {{done|Produce one specific piece of QA swag to deploy to contributors}} [marcia]
** {{ok|Design a QA contributor swag pack}} [marcia] -> Stretch Goal
** {{miss|Design a QA contributor swag pack}} [marcia] -> Stretch Goal
** {{ok|Keyword/flag created in Bugzilla/Github to track nominations for swag}} [kthiessen]
*** This was a stretch goal I did not have time to complete.
** {{done|Keyword/flag created in Bugzilla/Github to track nominations for swag}} [kthiessen]
* Events
* Events
** {{done|Define QA Participation in first MozCamp by participating in Content Design session}} [marcia]
** {{done|Define QA Participation in first MozCamp by participating in Content Design session}} [marcia]
** {{miss|Reinvigorate Test Days}} [aaronMT/ashughes/]
** {{miss|Reinvigorate Test Days}} [aaronMT/ashughes/]
*** {{risk|Instead of "reinvigorating" the entire test day, focus on providing a roadmap and a set of curricula to help other community leads to start doing the "reinvigorating" of the test days throughout Q3/Q4}}
*** {{miss|Instead of "reinvigorating" the entire test day, focus on providing a roadmap and a set of curricula to help other community leads to start doing the "reinvigorating" of the test days throughout Q3/Q4}}
** {{ok|Develop an Events Strategy}} [marcia] -> Stretch Goal
**** Significant progress has been made but roadmap definition will overlap into early Q3 with the intent to kickstart fixing our lowest-hanging fruit by end-Q3 and building on that in Q4.
** {{miss|Develop an Events Strategy}} [marcia] -> Stretch Goal
*** This was a stretch goal I did not have time to complete.
* Education/Resources
* Education/Resources
** {{ok|Start a "[[QA/Contribute/QA_101|QA 101]]" working group in consultation with the CBT Education Working Group, with emphasis on creating curriculum for teaching Mozillian contributors generally applicable QA skills}} [kthiessen]
** {{done|Start a "[[QA/Contribute/QA_101|QA 101]]" working group in consultation with the CBT Education Working Group, with emphasis on creating curriculum for teaching Mozillian contributors generally applicable QA skills}} [kthiessen]
* Contribution Paths
* Contribution Paths
** {{ok|Develop 1 or more clear contribution paths per team}} [Everyone]
** {{done|Develop 1 or more clear contribution paths per team}} [Everyone]
*** [https://wiki.mozilla.org/QA/Execution/Web_Testing/Contributor_levels Web QA]
*** [https://wiki.mozilla.org/QA/Execution/Web_Testing/Contributor_levels Web QA]
*** [https://wiki.mozilla.org/QA/Services/Contribute Draft for Services Team]
*** [[QA/Services/Contribute/Manual Testing|Manual Testing with the Cloud Services QA Team]]
*** [https://quality.mozilla.org/teams/desktop-firefox/ Desktop]
*** [https://quality.mozilla.org/teams/desktop-firefox/ Desktop]
**** Detailed path guide [https://wiki.mozilla.org/QA/Desktop/Community#Casual_Contributor WIP] will be complete by June 19th
**** Detailed path guide [https://wiki.mozilla.org/QA/Desktop/Community#Casual_Contributor WIP] will be complete by June 19th
*** FF for Android (https://etherpad.mozilla.org/QA-FXAndroidContributor-Pathways)
*** FF for Android (https://etherpad.mozilla.org/QA-FXAndroidContributor-Pathways)
*** FX OS
*** [https://wiki.mozilla.org/QA/FXOS/Contributor_levels FX OS]
canmove, Confirmed users
7,108

edits