Please note: Contributor levels are based on the larger Mozilla Community.
Manual Testing in the Cloud Services QA Community
It's easy to get started helping out the Cloud Services QA team. Start off with some of the tasks listed below to learn more about our team. We hope you get to know our projects and our community - there is a lot to do, and a lot of fun people to do it with. Improve your skills and help out Mozilla at the same time.
Become a casual contributor to our team! A casual contributor is someone who has volunteered small amounts of time in an activity. It shows you have made an initial investment in our team. Requirements include at least one of the listed examples. We would love for you to join us!
- Mission impact: In aggregate, casual contributors create real value for the improvement of Cloud Services QA projects and Mozilla, spreading the word, providing decision-informing data and more.
- Estimated size: Hundreds to thousands of people.
Before you start, you should have:
- A computer or device with Internet access,
- The Nightly version of Firefox,
- An email address where we can reach you, and
- Working knowledge of IRC, including some way to access it.
- Attend a Cloud Services QA test day! Look for Marketplace or other Cloud Services QA events on the QMO Events page
- Complete a Cloud Services QA One and Done task
Level up by taking on more responsibility, we have more tasks for you to learn new skills and help out the team. An active contributor is someone who has volunteered substantial time performing Cloud Services QA activities that involves interactions with others within the last 1 or 2 months. Requirements include one or more of the listed examples.
- Mission impact: Active contributors directly support Cloud Services QA through their contributions of time and skill and provide the team with the ability to move forward with a wide range of projects.
- Goal size: 25 - 30 people
- Join our Cloud Services QA Mailing list
- Attend and participate in multiple test days for Marketplace or Cloud Services QA
- File at least 3 bugs on Cloud Services QA projects in a 3-month period.
- Lead manual testing for a feature release. Start running manual tests and contact a project team member to ask about taking on manual testing.
- Mentor a community member by helping them get started with manual testing.
This level reflects a big commitment to the Cloud Services QA team. A core contributor is someone who has a leadership position on the Cloud Services QA team. We are happy to help you find the tasks that can lead to this level- you need to bring the motivation to work! Requirements include one or more of the listed examples.
- Mission impact: Core contributors make major impacts on Cloud Services QA projects through their contributions of time, skill and leadership.
- Goal size: 6 - 12 people
- Cloud Services QA project lead, someone who can be the primary tester on one of our projects, and can coordinate release testing. This can be a lead for automated or manual testing.
- One testing contribution (test case, filed bug, documentation note, participation in testing conversation) per week for an entire release cycle (6 weeks).
- Attends team meetings at least three times per quarter.