Desktop QA Standup - May 14th, 2014

Dial-in Information

• Wednesdays, 8:30am Pacific Time
• Telephone:
• 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 Guest URL
• Agenda and notes: etherpad
• Archives: wiki.mozilla.org
• Previous Meeting: https://wiki.mozilla.org/QA/SoftVision/Meetings/Desktop:2014-05-07

Attendees: mwobensmith, KaiRo, Cornel, Bogdan, Andrei, Alexandra, Otilia, Catalin, Mihaela, Petruta, Camelia, juanb

Heads-Up

• Upcoming PTOs:
  • juanb - PTO - May 21-26
  • lizzard May 22-26 (PTO for 22/23)
  • Cornel - May 23

• Events

Upcoming Schedule

Previous Action Items

• Notify automation team when significant UI changes are about to happen.
  • How do we notify other than cc'ing whimboo?: qa-testsuite flag

Discussion Items

• thoughts on "root cause" project (https://docs.google.com/document/d/16OVgqQxsjMVpOHcAQ7B5py4BpahiEL24q6oo5pZy_bs/edit )
  • looking at reopened bugs + regressions, by component, in Core + Firefox (lizzard)
  • interested to see if there are particular hot spots where we might focus more QA attention.
  • should probably focus on Core -- I suspect "big" components like JS Engine and Graphics need better attention -- in particular we have next to no regression coverage for WebGL -- Firefox probably has good coverage given all teams are on the Iterative Development process now (ashughes)
  • template for bug investigation: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Au-Dw_f8snrydDhseUczVFY0Z2pmSnMwc2JYdG5McEE&usp=sharing#gid=0

• iterative development process (ashughes)
  • engineering seems to have bought in to setting qa+/- as part of the planning/work selection process when the answer is known -- this should help ease the triage burden and noise in bugzilla
  • we'll still have qa? bugs for the meantime but how do people feel about deprecating that as a catch-all, use it as an uncertainty flag -- anything without a qa tag with an iteration tag would essentially act as our funnel +1

Channel Status

Beta (Fx 30) (Tracy/KaiRo)

• beta4 was delayed 'til today due to build issues.

Aurora (Fx 31) (Anthony/Liz)

Nightly (Fx 32) (Juan/Kamil)

ESR (Fx 24.5)

Security

• Ongoing pkix testing, beginning key pinning tests also

Automation

• All prioritized projects have project pages now, and leads have been defined
• Automation Training: the next training day will happen on May 21st
• TPS: Started to investigate location and neccessary VMs for CI - Request for machines will happen today
• Test creation: We setup the list for tests we want to automate this quarter: https://bugzilla.mozilla.org/show_bug.cgi?id=1007559
• We do not get pulse notifications for release / beta releases!! https://bugzilla.mozilla.org/show_bug.cgi?id=1010120

Stability

• Some looks at beta 29 -> beta 30 regressions via https://crash-analysis.mozilla.com/rkaiser/2014-05-06/2014-05-06.firefox.beta.explosiveness.html
  • The libinject issue we already know and are blocking is the main one visible
  • Two signatures related to plugin shutdown are the only other real concern
  • A few items with pretty low volume might merit bugs, but not active tracking.
• We had some ADI issues over the weekend that influence crash rates; road to new ADI servers on Nightly is a bit bumpy, working with metrics to smoothen this out

Community

Welcome to Maja who will be working on One and Done project with lizzard, bsilverberg, bitgeeky, and rbillings as one of QA's GNOME-OPW interns this summer.

Maja is taking time off from  teaching CompSci to kick-start her contributions to open source and  learn about modern web development. She's been teaching college-level CS  for the past 3 years and before that worked on compilers research as  part of her graduate degree in CS+Math.   (http://www.majazf.ca/blog/)

Notes and Actions

• root cause project, list of areas, some numbers
• absence of qa flag means qa?; qa+/- happening during iteration triage, getting better
• need to finalize which tags/flags we will use so we can communicate them broadly and start using them