The role of Mozilla’s Web QA team is to ensure the quality of our web applications across a variety of platforms and browsers. We work on a wide variety of projects, aiming for high quality and timely releases of our user facing sites.
How to Get Involved
It’s great that you want to get involved with the Web QA team, and we would love to have you as a contributor!
The easiest way to get started is to join us on IRC and we’ll be happy to guide you though the process. Just join #mozwebqa on irc.mozilla.org, say hi, and let us know you’re there to help. You can also send us an email at email@example.com and someone will get back to you.
For some more information about manual testing, check out this overview.
Our automated tests use Selenium and Python. If you are familiar with either of them we can use your help, and helping us is a great way to learn more. The steps to get started with automation include:
All of our automation efforts are organized based on the sites that are being tested, with each site having its own project. Your first step, therefore, is to choose a project to work on. You can explore our projects to find one that interests you, but if you’re just looking for a simple place to start we suggest mcom-tests.
Your next step should be to grab a copy of the tests for your chosen project and try to run them. You can find all the details for doing this in our Running Web QA Tests guide.
If you are interested in helping with security testing, check out the security testing page on our wiki.
- A brief introduction to POM from the Selenium site.
- If you would like to write some automated checks for us, you will need to be familiar with version control through GitHub, programming in Python and writing automated checks in Selenium. We recognize that volunteering is always a learning opportunity, so here are a few of our favorite resources if you need to refresh what you know or learn something new before contributing:
- As you begin writing checks, please adhere as closely as possible to the Style Guide, so we’re all on the same page, and reviews go more smoothly.Once you’ve written your tests, they will go through our Code Review process.
- File bugs to help us improve the product (Learn how to file bugs here).
Talk to Us!
We would love to hear from you. Here are various ways of reaching and/or finding out more information: