QA/Desktop Firefox/StaffMeetings/Desktop-QA-Staff-07-16-2013: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "Desktop QA Meeting 650-903-0800 or 650-215-1282 x92 Conf# 99779 (US/INTL) 1-800-707-2533 (pin 369) Conf# 99779 (US) Vidyo Room: QA-Desktop Vidyo: https://v.mozilla.com/flex...")
 
No edit summary
 
Line 9: Line 9:
Announcements
Announcements


    Summit Travel booking is now available.
* Summit Travel booking is now available.
    [juanb] - PTO for Aug 8 - 26  
* [juanb] - PTO for Aug 8 - 26  
    [tracy] - PTO July 16 - 23
* [tracy] - PTO July 16 - 23
    [mwobensmith] - PTO July 25 - Aug 3
* [mwobensmith] - PTO July 25 - Aug 3
* Testday this Friday: https://quality.mozilla.org/2013/07/firefox-23-0-beta-7-testday-july-19th/


Agenda
Agenda


* Goals
Goals
    Time to start working on Goals for Q3
* Company goals (Q3) https://intranet.mozilla.org/2013Q3Goals
    Documentation for new hires, interns and community
* QMO page update - Single point of entry: Tracy to drive project
    https://intranet.mozilla.org/QA/Q22013_QAgoals
    Company goals (Q2) https://intranet.mozilla.org/2013Q2Goals


* Whats New in Firefox
Whats New in Firefox
*
* Multiple beta process - so far so good.
*   Knowledge sharing
* fewer changes in each beta - lets us focus more on those changes for each release.
**    Anthony Hughes: mozmill ondemand test automation (Anthony needs to make a video)
*    Issues/Blockers
**
*    Round Table


    [ashughes] Can we support testing "touch" as a release criteria?
Knowledge sharing
    UPDATE: not an urgent concern but we shouldn't delay in planning
    See bug 736048 and bug 888304 for context
    Est. ~30% of our Windows users will be using touch-enabled PCs by year's end
    Platforms: Windows 7+
    Devices: TBD by Asa
    Proposed (has support of devs & Asa):
    Reach out to our Nightly Tester and QMO communities (as well as internal - ie. Engineering) for greater dogfooding support
    Add "touch" to our Beta checklist and test in at least one Beta every 6 weeks
    Engineering ensures critical bugs are on QA's radar with qawanted and verifyme keywords
    Add some Mozmill tests to cover the most common use cases (Mozmill should support touch-events later this quarter)
    Organize a testday once market penetration of devices is greater (probably early 2014)
    [juanb] Should we? For how  many cycles? If there's no churn in this code, can we check initially  (verify for a couple of cycles) but then rely on automated coverage?
    I think so, essentially it needs to get the same QA support as mouse events work


* Anthony Hughes: mozmill ondemand test automation
** https://wiki.mozilla.org/QA/Desktop_Firefox/Releases/Walkthrough#Functional_Automation
Issues/Blockers
* Vacation coverage plan
** Samvedana will cover metro, Anthony will cover ESR releases.
* Duties for new softvision position
** ashughes has gaming test plan out for review and will document basic WebRTC tests to be included as well.
Round Table
* Can we do one of our meetings on air.mozilla one week to see how it goes
** "Current meeting notes are usually sufficent, shoud make notes more discoverable on the wiki and improve the notes taken during the meeting"
* Policies on verification w/r/t debug/release and platform [mwobensmith]
Notes
Notes
Previous Action Items
Previous Action Items
Line 51: Line 49:


New Action Items
New Action Items
* mschifer - follow up on air.mozilla usage
* ashughes - take survey on qmo for interest in air.mozilla recordings of our meetings

Latest revision as of 21:37, 22 July 2013

Desktop QA Meeting 650-903-0800 or 650-215-1282 x92 Conf# 99779 (US/INTL) 1-800-707-2533 (pin 369) Conf# 99779 (US) Vidyo Room: QA-Desktop Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=RU7dVysDFakY Archive: https://wiki.mozilla.org/QA/Desktop_Firefox/StaffMeetings#Meeting_Details Attendees

Announcements

Agenda

Goals

Whats New in Firefox

  • Multiple beta process - so far so good.
  • fewer changes in each beta - lets us focus more on those changes for each release.

Knowledge sharing

Issues/Blockers

  • Vacation coverage plan
    • Samvedana will cover metro, Anthony will cover ESR releases.
  • Duties for new softvision position
    • ashughes has gaming test plan out for review and will document basic WebRTC tests to be included as well.

Round Table

  • Can we do one of our meetings on air.mozilla one week to see how it goes
    • "Current meeting notes are usually sufficent, shoud make notes more discoverable on the wiki and improve the notes taken during the meeting"
  • Policies on verification w/r/t debug/release and platform [mwobensmith]


Notes Previous Action Items

   None

New Action Items

  • mschifer - follow up on air.mozilla usage
  • ashughes - take survey on qmo for interest in air.mozilla recordings of our meetings