QA/COG: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
 
(11 intermediate revisions by the same user not shown)
Line 4: Line 4:


=== FYI on Communication ===
=== FYI on Communication ===
* Actively engage with community members in a positive and non-curt manner
* Actively engage with community members in a positive and engaging manner
* Always ask questions if there is the '''slightest''' bit of uncertainty
* 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
** If they don't answer back after a certain amount of time, ask if they're confused about something
Line 10: Line 10:


=== Initial Introduction for New Community Members ===
=== Initial Introduction for New Community Members ===
* If they have a specific interest in a specific area
# If they have a specific interest in a specific area
** Give them an e-mail address for one of the following mappings:
#* Give them an e-mail address for one of the following mappings:
*** If WebDev: '''stephend'''
#** If WebDev: '''stephend'''
*** Community Involvement: '''aakashd''', '''juanb'''
#** Community Involvement: '''aakashd''', '''juanb'''
*** Data Analysis: '''murali'''
#** Data Analysis: '''murali'''
*** Localization: '''tchung''', '''juanb'''
#** Localization: '''tchung''', '''juanb'''
*** Mobile: '''jmaher'''
#** Mobile: '''aakashd'''
*** OS Testing: '''marcia'''
#** OS Testing: '''marcia'''
*** Triaging: '''tracy'''
#** Triaging: '''tracy'''
*** Unit Testing/Automation/Tool Development: '''ctalbert'''
#** Unit Testing/Automation/Tool Development: '''ctalbert'''
*** Website Testing: '''whimboo'''
#** Website Testing: '''whimboo'''
*** MozMill: '''whimboo'''
#** MozMill: '''whimboo'''
* If no specific interest, ask them to go through [http://quality.mozilla.org/projects QMO's Projects] page and see if there is something they are interested in
# If no specific interest, ask them to go through [http://quality.mozilla.org/projects 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 [https://addons.mozilla.org/en-US/firefox/addon/5428 QAC] and tell them to e-mail '''you''' the BFT they are interested in
#* If nothing interests them from the list of Projects on QMO, suggest Litmus BFTs via [https://addons.mozilla.org/en-US/firefox/addon/5428 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'''
#** Once they have determined a subgroup, forward their e-mail to '''tracy'''


* In general:
* In general:
Line 33: Line 33:


=== Determining the Next Step ===
=== Determining the Next Step ===
* In the beginning
# In the beginning
** Offer a simple assignment (to determine their level of competency) and reading material about the subject in QMO's Doc Tree
#* 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
# After enough initial competency check
** Continue to give them more authority and responsibility when they are ready for it
#* Continue to give them more authority and responsibility when they are ready for it
** Don't be afraid to let them make mistakes
#* Don't be afraid to let them make mistakes
 


=== Preliminary Task List ===
=== 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.  
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 should be designed to develop someone who doesn't have much experience at all in testing, web development languages and/or the Mozilla community.


* WebDev
* WebDevQA
* Community Involvement
* Community Involvement
** Assist in testday and bugday promotions via social networking
** Assist in testday and bugday promotions via posting to social networks
** Write technical documentation on the [http://wiki.mozilla.org/QA/QMO/DocsNeeded these topics]
* Data Analysis
* Data Analysis
* Localization
* Firefox
** Download a build in your language and run the 3.x l10n localizer Litmus test run.
** Running litmus tests via QA Companion
** Learn to follow through the bug filing process by participating in bug days on thursday
* Mobile
* Mobile
** Download the build from the [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mobile-1.9.2/ mobile nightly builds] page and run BFT checks on a Fennec [http://litmus.mozilla.org Litmus] test run
** [https://wiki.mozilla.org/QA/Fennec#Where_Do_We_Need_Help Things We Need Help With]
* OS Testing
* OS Testing
* Triaging  
* Triaging  
Line 56: Line 57:
* Website Testing
* Website Testing
* Unit Test Automation
* Unit Test Automation
** [https://wiki.mozilla.org/QA/TDAI/Projects#Tests_that_Need_to_Be_Written Write Testscripts] for a select few
* MozMill Automation
* MozMill Automation
* Labs extension testing
* Labs extension testing
** Weave sync beta will be out.  Can get the builds through addons manager or AMO
** Download Weave through the addons manager or AMO.
** Participate in testday on 12/4
* Running litmus tests via QAC. Find and file at least 5 bugs into bugzilla (folks will create litmus/bugzilla accounts, and learn to follow through the bug filing process)

Latest revision as of 22:10, 9 February 2010

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 engaging 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

  1. 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: aakashd
      • OS Testing: marcia
      • Triaging: tracy
      • Unit Testing/Automation/Tool Development: ctalbert
      • Website Testing: whimboo
      • MozMill: whimboo
  2. 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

  1. In the beginning
    • Offer a simple assignment (to determine their level of competency) and reading material about the subject in QMO's Doc Tree
  2. 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 should be designed to develop someone who doesn't have much experience at all in testing, web development languages and/or the Mozilla community.

  • WebDevQA
  • Community Involvement
    • Assist in testday and bugday promotions via posting to social networks
    • Write technical documentation on the these topics
  • Data Analysis
  • Firefox
    • Running litmus tests via QA Companion
    • Learn to follow through the bug filing process by participating in bug days on thursday
  • Mobile
  • OS Testing
  • Triaging
  • Tool Development
  • Website Testing
  • Unit Test Automation
  • MozMill Automation
  • Labs extension testing
    • Download Weave through the addons manager or AMO.
Retrieved from "https://wiki.allizom.org/index.php?title=QA/COG&oldid=201222"