QA/COG

From MozillaWiki
Jump to navigation Jump to search

QA Community Outreach Guide

Purpose

  • To help provide direction to new Mozilla QA community members via a simple and concise guide for QA Community Leaders

FYI on Communication

  • Actively engage with community members in a positive and non-curt manner
  • Always ask questions if there is the slightest bit of uncertainty
    • If they don't answer back after a certain amount of time, ask if they're confused about something
  • Always answer questions promptly and concisely

Initial Introduction for New Community Members

  • If they have a specific interest in a specific area
    • Give them an e-mail address for one of the following mappings:
      • If WebDev: stephend
      • Community Involvement: aakashd, juanb
      • Data Analysis: murali
      • Localization: tchung, juanb
      • Mobile: jmaher
      • OS Testing: marcia
      • Triaging: tracy
      • Unit Testing/Automation/Tool Development: ctalbert
      • Website Testing: whimboo
      • MozMill: whimboo
  • If no specific interest, ask them to go through QMO's Projects page and see if there is something they are interested in
    • If nothing interests them from the list of Projects on QMO, suggest Litmus BFTs via QAC and tell them to e-mail you the BFT they are interested in
      • Once they have determined a subgroup, forward their e-mail to tracy

Determining the Next Step

  • In the beginning
    • Offer a simple assignment (to determine their level of competency) and reading material about the subject in QMO's Doc Tree
  • After enough initial competency check
    • Continue to give them more authority and responsibility when they are ready for it
    • Don't be afraid to let them make mistakes


Preliminary Task List

This task list is not a finite set of tasks each person will be forced to do when joining the community. It's a set of specific tasks a new community member will be able to complete within a short amount of time. Each task is designed to help someone that doesn't have much experience at all in matters of testing, web development languages and/or the Mozilla community become familiar with such things.

  • WebDev
  • Community Involvement
    • Assist in testday and bugday promotions via social networking
  • Data Analysis
  • Localization
    • Download a build in your language and run the 3.x l10n localizer Litmus test run.
  • Firefox
    • Running litmus tests via QAC
    • Find and file at least 5 bugs into bugzilla
    • learn to follow through the bug filing process
  • Mobile
  • OS Testing
  • Triaging
  • Tool Development
  • Website Testing
  • Unit Test Automation
  • MozMill Automation
  • Labs extension testing
    • Weave sync beta will be out. Can get the builds through addons manager or AMO
    • Participate in testday on 12/4