QA/Team Meeting/QA Team Meeting-2014-10-22

From MozillaWiki
Jump to: navigation, search

Mozilla QA Meeting: Wednesday, October 22

# Every Weds @ 1:30p Pacific Time - Mozilla HQ, Room: QA
#
# Vidyo:  https://v.mozilla.com/flex.html?roomdirect.html&key=nL4PESn1IaVh
# Phone:  +1 650 903 0800 or 650-215-1282 x92 Conf# 9245 (US/INTL)
#         +1 800 707 2533 (pin 369) Conf# 9245 (US Toll Free)
#         +1 416 848 3114 x92 Conf# 9245 (Canada)
# IRC:    irc://irc.mozilla.org:6697/#qa

Template available at: https://wiki.mozilla.org/QA/Team_Meeting/QA_Team_Template

Actions From Last Week

Discussion Zone

  • Pick a notetaker for our notepad
  • Profiler and Mozmill Training last week. How useful was that to those who attended and what would you like to see done in the future?
  • Tiles load testing update.
  • 33.0.x/33.1/34.0 schedule
  • What can we do to help catch these kind of issues in the future.

QA Show and Tell

Updates, Milestones, Deadlines (2min each call to action)

  • Samples:
    • A call to action: [TAKE ACTION] <Information> For more information contact: <Contact Person>
    • A notice of information (will be read only so make it complete, but don't write a novel): [FYI] <Information>
    • [TAKE ACTION] Please take part, as you can, in the Fx33.1 dogfooding program. We'll be sending out new challenges every couple of days. For more information contact: Tracy
    • [TAKE ACTION] Please add links to test for functional areas you own in the following etherpad. For more information contact: juanb

Upcoming Events

Community

QMO Re-design 2014

Contributor Spotlight

These are new contributors, if you see them around, say hello

Contributor Honor Roll

For those that went above and beyond this week, we salute you here.

Quarter Goals

Action Items and notes from the meeting

  • Please bold action items.
  • good feedback from those attended both the Profiler and Mozmill training:
    • wish it were longer (some)
    • others wished it were more hands-on
    • install your own, write your own test, have a prepared (bad) test to debug
    • immediacy (not useful for everyone right now. useful in 3 months)
    • call out the pre-reqs a bit better (vpn access for mozmill-ci, etc)
  • other feedback about types of requested training:
    • (desired) high-level overview of our testing frameworks + their uses (MDN lists some)
    • Advanced/useful Bugzilla querying
    • perhaps a refresher on Moztrap?
    • how to make the best use out of Air Mozilla, across QA
    • intro to debugging, using wireshark, etc

Tiles load testing:

  • takeaway from anything that depends on Services/Websites:
    • ask questions/coordinate/double-check that a feature in Firefox/elsewhere doesn't depend on a service/website, or -- if it does -- that it's covered with backend/integration testing, or called out as a risk
  • find out how we can tell if a particular machine/graphics card is in the slow path (<--- liz, help! did I capture this right?) I am not sure what people we're talking about here. - liz
  • Firefox releases:
    • have a little less than 1 1/2 weeks to get ready for the 33.1 release deadline
    • please use the Alder branch as your primary test build for the forseeable future
    • please sign up for the Firefox 10-year anniversary mailing list for testing challenges
    • should see localized tiles for your particular locale
  • Ways we can help catch graphics/other issues in the future:
    • see if you can help come up with ideas to try to catch graphics-card issues in the wild
      • feel free/encouraged to email qa@mozilla.org / post to mozilla.dev.quality (goes to the same place, so no need to post twice)
    • push the bug filed last year, filed to audit blacklisting (aaron)
    • downgrading video drivers. how to. we need documentation.... (kevin)
    • support after crash? (or in FHR)
  • perhaps we should get graphics-driver information into about:support (kairo) +1!!!
  • advocate for ability for end user to turn off risky feature (via pref) in the future?
  • not enough data, typically, to back up our risk-assessed push-back decisions, from betas
    • then we get burned in release
    • what kind of mechanisms can we get in place, to help validate our push-back and quality assessments, going forward?
    • lots of data point to a combination of integrated chipset with an additional video card -- most-evidenced in laptops
    • we're examining the most-common/most-problematic configurations (at least from SUMO/Socorro)
    • we should look into what Telemetry data can provide us, as well
  • Request from Juan:
    • get your Firefox feature tests, per area (in whatever form they exist), over to Juan, so he can build out the E10S test-suite
  • We will take notes on this etherpad

Travel / PTO

  • juanb: PTO Oct 24 - Nov 2
  • KaiRo out this Friday (Oct 24) for GSoc Reunion, and out Wed Oct 29 for flying back to Vienna.

For Further Information

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.

Firefox QE

  • Who we are: Individuals focused on Firefox Desktop, Firefox Android, and Gecko Platform Quality
  • Meetings held weekly on Wednesdays at 8:30AM Pacific Time
  • To Join:
    • Vidyo:
    • Phone (use any of these):
      • 1-650-903-0800 or 1-650-215-1282 US/INTL
      • 1-800-707-2533 Toll Free US/Skype
      • If using a 650 number, use Extension: 92
      • If using the 1-800 number, use PIN: 369
      • Conference Number: 99779
  • Meeting Notes Archive
  • Next Agenda: No published agenda

Firefox OS

Services QA

  • Who we are: Individuals focused on Quality of the services that power features of all products
  • Meetings held weekly on Mondays at 3:30PM Pacfic Time
  • To Join:
    • Vidyo
    • Phone (use any of these):
      • 1-650-903-0800 or 1-650-215-1282 US/INTL
      • 1-800-707-2533 Toll Free US/Skype
      • If using a 650 number, use Extension: 92
      • If using the 1-800 number, use PIN: 369
      • Conference Number: 9245
    • IRC: irc://irc.mozilla.org:6697/#qa
  • Meeting Notes Archive: No archive
  • Next Agenda: No published agenda

Web QA

  • Who we are: Individuals focused on maintaining the Quality of Mozilla's web properties, and improving the core QA websites we all use.
  • Meetings held weekly on Thursdays at 9:00AM Pacific Time
  • To Join:
    • Vidyo
    • Phone (use any of these):
      • 1-650-903-0800 or 1-650-215-1282 US/INTL
      • 1-800-707-2533 Toll Free US/Skype
      • If using a 650 number, use Extension: 92
      • If using the 1-800 number, use PIN: 369
      • Conference Number: 9303
    • IRC: irc://irc.mozilla.org:6697/#mozwebqa
  • Meeting Notes Archive
  • Next Agenda: No published Agenda

Platform QA

Community Champions

  • Who we are: Individuals from every aspect of QA focused on improving all aspects of our community involvement
  • Meetings held every other Friday 1:00PM Pacific
  • To Join:
    • Vidyo
    • Phone:
      • 1-650-903-0800 or 1-650-215-1282 US/INTL
      • 1-800-707-2533 Toll Free US/Skype
      • If using a 650 number, use Extension: 92
      • If using the 1-800 number, use PIN: 369
      • Conference Number: 9214
  • Meeting Notes Archive
  • Next Agenda: No Published Agenda

Crashkill

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Team_Meeting/QA_Team_Meeting-2014-10-22&oldid=1027972"