QA/Team Meeting/QA-Team-09-03-2014

From MozillaWiki
Jump to: navigation, search

Mozilla QA Meeting Sept 3, 2014 (Video Replay)

# 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

Actions From Last Week

  • [DONE] Liz to send out how to use snippets
  • [ON TRACK] Geo to send out how to record these meetings
    • Added to intranet wiki, will send email
  • [DONE] Ctalbert to fix the meeting template
  • [ON TRACK] Everyone to try out E10S builds on nightly
  • [DONE] Clint and Matt to meet up about moztrap
  • [ON TRACK] Ctalbert to ping airmo folks again

Discussion Zone

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>

Upcoming Events

Community

  • QMO Redesign
    • First documentation sprint will be this Friday at 10 AM Pacific.
    • Everyone should have an invite to that meeting on their calendar

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

What do goals look post reorg? To get to goals we need a common language to approach quality at Mozilla. @ https://etherpad.mozilla.org/QA-Quality-Foundations


Delight - meets or exceeds the expectations of the user. Goal for this discussion is to name the buckets. context driven testing - what is the quality bar we are targeting? -- (example: KaiRo's measure of whether we are "stable enough" -- How/where do we record what the standards are that we're aiming for ?


Thresholds pass/fail criteria - need regular updating.


Quality is: you know it when you see it. Defining quality as a set metric is impossible. You can set ranges metrics should fall into.


We could track values for areas of bugzilla and create a total score for the area. This would give us insight into the health of the area.


Do the 5 areas outline the framework that we can use discuss the goals? Are there any missing areas? Does the "Web Platform" section apply to quality metrics. Discussion about do we hold a release for not pushing the web platform forward?


Hard blockers. Having a team definition of quality (outside the quality team). Our team should be an example for external teams. We can represent and highlight our tools and processes as part of our civic presence in open source software and for other QA teams in other projects.


Convincing product/project/dev the value of the small bug, death of 1000 paper cuts. Mentor bugs is a way to move a chunk of these forward. UX can be an ally. Make a case to project that a sprint should be dedicated to cleaning up polish bugs. Can be useful for devs to knock off a larger number of bugs.


Jobs with a rather different common vocab is going to be difficult. Especially with outside teams. What language do we need to use to communicate the state of quality to external teams? Does talking about quality need a model? Should we start from scratch. Definitely need vocab and need to be persuasive.


Deliverables? Feedback on model Feedback on idea of how to do these large discussion meetings Quantifying Quality

  • Quality is first-and-foremost user perception!
  • You know it when you see it
  • Poor Quality - Easy to identify. Often more a "measure of complaints"

Articulating Quality Not Just Data/Metrics

  • Not: "what are the right metrics"
  • we're making all these observations now (and can always improve upon...)

Purpose of Common Language/Vocabulary

  • Ability to articulate my user experience in a language anyone can understand
  • We're not the only ones observing quality & our jobs are all so different
  • Talking about quality using common themes or reference frame could enable us to make a better case for things like polish (vs. just function).

Travel / PTO

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

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-09-03-2014&oldid=1013175"