QA/Execution/Web Testing/Contributor levels
Who Is In The Web QA Community
An overview of the Web QA Community based on the larger Mozilla Community.
Who Is In The Web QA Community
It's easy to get started helping out the Web QA team. Start off with some of the tasks listed below to learn more about our team, and to earn some cool badges! 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 Web QA projects and Mozilla, spreading the word, providing decision-informing data and more.
- Estimated size: Thousands of people
- Join our Web QA Mailing list
- Attend a Web QA test day! Look for Marketplace or other Web QA events on the QMO Events page
- Earn one of our Web QA team badges
- Join our Mozillians Web QA group: https://people.mozilla.org/en-US/group/webqa/ (was)
- Comment on one of our GitHub team projects, or submit a pull request on a Web QA team repo
- You can't complete now:
Completing any of the tasks above makes you eligible for our first team badge. Apply here https://badges.mozilla.org/en-US/badges/badge/Web-QA-Enthusiast . Make sure to enter your info on the form!
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 Web 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 Web QA through their contributions of time and skill and provide the team with the ability to move forward with a wide range projects.
- Goal size: 25 - 30 people
- Attend and participate in multiple test days for Marketplace or Web QA
- File at 10 bugs on Web QA projects
- Lead manual testing for a feature release. Start running manual tests and contact a project team member to ask about taking on manual testing.
- Have 3 pull requests merged on Web QA projects
- Mentor a community member by helping them get started with automation or manual testing.
Completing any of the tasks above makes you eligible for our second team badge. Apply here https://badges.mozilla.org/en-US/badges/badge/Web-QA-Apprentice . Make sure to enter your info on the form!
This level reflects a big commitment to the Web QA team. A core contributor is someone who has a leadership position on the Web 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 Web QA projects through their contributions of time, skill and leadership.
- Goal size: 8 - 10 people
- Web 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.
- Web QA community builder, someone who rallies our community and actively works with new contributors.
- Web QA Automation core contributor, someone who regularly makes pull requests and comments on one or many of our GitHub project repos.
- Web QA Automation mentor, someone who comments on new contributor commits helping them learn the styleguide and encouraging them to participate.
Completing any of the tasks above makes you eligible for our third team badge. Apply here: https://badges.mozilla.org/en-US/badges/badge/Web-QA-Sorceror. Make sure to enter your info on the form.