A high level guide on how to contribute to Firefox Quality Assurance. Each level of contribution is generally outlined at Firefox QA Community. Read on if you are a Firefox user and are interested in becoming at least a Casual Contributor, if not an Active or Core Contributor.

What is there to do?

There is prolific growth in and production from the Mozilla Development Community. Mozilla QA could use your help to keep up with that growth and production. Firefox QA is one area where you can make an impact. What follows are ways to take action and make an impact at each of the higher levels of the Firefox QA Community.

Casual Contributor

The easiest ways to contribute to the Firefox QA Community are to take a few moments to do one or more of the following.

• File bugs when you encounter them. This is an excellent resource to learn how.
• Always submit any Firefox crash reports.
  • What is Crash Reporting?
  • By submitting crash data, our analyst will identify trends and get a workable bug on file for the developers to fix.
• Share your thoughts about Firefox at input.mozilla.org. Understanding what our users enjoy using or not helps Mozilla make their products better.
• Look up or file a support ticket on an issue you have with Firefox at SUMO. By observing how support issues are trending, Mozilla can identify top issues and correct them in our products or services.

Yes, it is that easy! Nothing too complicated or time consuming. Just take a moment to get involved.

Active Contributor

Make a bigger impact by taking part directly with regular Firefox QA activities. What follows are contributor pathways to learn about, grow your skills in and actively contribute to Firefox QA.

• Get comfortable installing and using Desktop Firefox from Firefox builds across all Channels; Nightly, Aurora, Beta, Release and ESR.

• (Bugmaster) Become skilled at working in Bugzilla.
  • Thing to do 1 <- needed
  • etc <- needed
• Tester
  • Join us in IRC: #testday on irc.mozilla.org and run Moztrap tests or run them when you can.
    • Link to test run <- needed
    • Link to test run <- needed
  • Write manual test cases for MozTrap.
    • list of test cases <- needed

• Get involved with the QA Automation team.
  • Thing to do 1 <- needed
  • etc <- needed

• Community building
  • Grow a Mozilla QA Community in your area
  • Help others grow their skills and knowledge on IRC
  • Join the QA Community call. <- needed

• Help keep Firefox QA Documentation up to date.
  • Thing to do 1 <- needed
  • etc <- needed

The time and effort for an active contributor is elevated quite a bit. Your contribution time can be as much or as little as you'd like, but probably at least a few hours per week.

Core Contributor

It is our goal to integrate more community members into Firefox QA as Core Contributors. A core contributor will have a broad base of knowledge from participation in many of the areas of an Active Contributor. He/she will be a trusted and highly valued member of the team.

• Feature Owner
  • Active Core contributor skills needed: Bugmaster, Tester, Documentation, Community
  • need document describing what is entailed in feature ownership

• Automation Mentor
  • Active Core contributor skills needed: Automation, Bugmaster, Documentation, Community
  • need ideas and documentation

• Community Mentor
  • Guide new contributors to Active Contributor pathways
  • Lead community growth efforts
  • Organize and facilitate Firefox Test Days.

A core Contributor can expect to put 10 - 20 or more hours per week towards Firefox QA.

What's Next?

Becoming a Casual Contributor is fairly self explanatory. However, if you want get more deeply involved in Desktop Firefox QA by becoming an Active Contributor, you'll need some guidance from a Core Contributor to get you going. Talk to Us!

We would love to hear from you. Here are various ways of reaching us:

• IRC: #qa on irc.mozilla.org
• Email: dev-quality@lists.mozilla.org <- is this where we want to point folks?
• Team Wiki: https://wiki.mozilla.org/QA/Firefox <- page needed
• Mailing list: what list do we want to point to?
• Contributor Corner: Our list of fantastic team contributors