QA/COG: Difference between revisions

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

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

In general:
- Bring up Testdays and BugDays
- Offer the following reading material
  - Litmus Tutorial
  - A Bug's Life Walkthrough

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 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
- Things We Need Help With
OS Testing
Triaging
Tool Development
Website Testing
Unit Test Automation
- Write Testscripts for a select few
MozMill Automation
Labs extension testing
- Download Weave through the addons manager or AMO.

@@ Line 1: / Line 1: @@
-== QA Community Outreach Guide [<FONT COLOR=RED>DRAFT</FONT>]==
+== 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
-=== "Tips to Live By" for MozQA ===
+=== FYI on Communication ===
-* Actively engage with community members as if it was your first priority. The QA community is a place to not only test Mozilla projects, but also enjoy your time in.
+* Actively engage with community members in a positive and engaging manner
-* Always ask questions if you don't understand what they mean
+* Always ask questions if there is the '''slightest''' bit of uncertainty
-** If they don't answer back after a certain length of time, make sure to 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
-* Always answer questions promptly and accurately, but with a teaching point of view
+* Always answer questions promptly and concisely
-* Remember it's not what they can help you with, it's what the Mozilla QA community can offer them and/or how we can get them to where they want to get at
 === Initial Introduction for New Community Members ===
-* After the end of the first conversation, either one of two things should happen
+# 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 the contact information of the mozQA member who is in charge of that area
+#** If WebDev: '''stephend'''
-**** If WebDev, have them read the [https://wiki.mozilla.org/QA/Execution/Web_Testing/Volunteer WebDev Volunteer Guide] and contact stephend via e-mail
+#** Community Involvement: '''aakashd''', '''juanb'''
-**** If Community Involvement, contact aakashd via e-mail
+#** Data Analysis: '''murali'''
-**** If Data Analysis, contact murali via e-mail
+#** Localization: '''tchung''', '''juanb'''
-**** If Localization, contact tchung via e-mail
+#** Mobile: '''aakashd'''
-**** If Mobile, contact jmaher via e-mail
+#** OS Testing: '''marcia'''
-**** If OS Testing, contact marcia via e-mail
+#** Triaging: '''tracy'''
-**** If Triaging, take part in Bug Days and/or contact tracy via e-mail
+#** Unit Testing/Automation/Tool Development: '''ctalbert'''
-**** If Unit Testing/Automation/Tool Development, contact ctalbert
+#** Website Testing: '''whimboo'''
-**** If Website Testing, contact whimboo via e-mail
+#** MozMill: '''whimboo'''
-*** After initial contact, offer a simple assignment to determine their level of competency (each person is in charge of determining a simple assignment) as well as reading material about the subject in QMO's doc tree
+# 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 run through Litmus test cases and find a subgroup they are interested in testing more
+#* 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
-*** Ask them to read "Litmus Tutorial", "Litmus Triaging Guidelines", "A Bug's Life Walkthrough" and "Bug Triaging Guidelines" Docs on QMO
+#** Once they have determined a subgroup, forward their e-mail to '''tracy'''
-*** Once they have determined a subgroup, allow them to vet 1-2 test reports/bugs within one of your own subgroups and determine their competency
+* In general:
+** Bring up Testdays and BugDays
+** Offer the following reading material
+*** [http://quality.mozilla.org/documents-home/test-docs/litmus-tutorial Litmus Tutorial]
+*** [http://quality.mozilla.org/bugs-life-walkthrough A Bug's Life Walkthrough]
 === Determining the Next Step ===
-* Once they have incubated in their beginning tasks and have confidence that they are ready to assist further, make sure to promote them by giving them more authority and responsibility.
+# In the beginning
-** Each person has different abilities and interests. Make sure to ask them if they're interested in some specific authority and see how they do
+#* Offer a simple assignment (to determine their level of competency) and reading material about the subject in QMO's Doc Tree
-** Once this authority is offered, you need to treat them as a valued member of the community who can be depended on
+# After enough initial competency check
-** If they ask for authority, give them a chance to deliver (and make some mistakes)
+#* 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 [http://wiki.mozilla.org/QA/QMO/DocsNeeded 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
+** [https://wiki.mozilla.org/QA/Fennec#Where_Do_We_Need_Help Things We Need Help With]
+* OS Testing
+* Triaging
+* Tool Development
+* Website Testing
+* Unit Test Automation
+** [https://wiki.mozilla.org/QA/TDAI/Projects#Tests_that_Need_to_Be_Written Write Testscripts] for a select few
+* MozMill Automation
+* Labs extension testing
+** Download Weave through the addons manager or AMO.