QA , quality assurance seems to be a very important part of a FLOSS project. It is not enough only to report bugs and “bad” issues , the question is how QA Team improves the software quality. So in each FLOSS project the QA team has to fill the following goals :
a) The product should be suitable for the intended purpose.
b) Mistakes should be eliminated.
Considering the goals above , Mozilla do have a strong QA. Let’s see:
Mozilla QA :
Mozilla’s QA is divided into teams focused on Mozilla product areas or technologies. My goal is to focus on the Community Contribution of each team.
The team focuses on testing current and upcoming releases of Firefox. Some of our responsibilities include qualifying builds prior to a maintenance or milestone release. Some of the responsibilities include:
- Verifying bugs
- Running basic functional tests and smoke tests – automated and manual
- Running our automated test suites on localized builds
- Running automated update tests across platforms, through all update paths, across localized builds
- Making sure web content is ready for consumption
As mentioned before i focus on the community contribution. Anyone can participate to the team , but they do exist several ways to do it , such as :
- File bugs
- Triage bugs (confirm existing bugs and assign them to the right buckets)
- Help test new features
- Write test cases
- Plan new features testing
- Help others who want to get involved.
Browser Technologies QA : The Browser Technologies Team mission is two-fold, they aim to improve the quality of Firefox and finely tune it for mobile devices as well as drive the testing efforts for all the Mozilla Labs projects, web services and web apps. As Mobile, Web Services, Labs, and Web Apps become more prominent in the Mozilla project, QA continues to strive to cover and test the projects forthcoming. Furthermore the Community Contribution part is similar to Desktop Firefox QA’s.
Web QA : Through a variety of tools and approaches, WebQA aims to ensure high quality web applications, of both external and internal applications and websites. The team’s structure differs from the other Teams. Likewise the Community , contributes in another way. The Community do participate in Testdays, when users are testing the claim of the bug and trying to reproduce it.
QA Automation Services : The Automation Services team is responsible for helping the QA teams on specific products excel at what they are doing using a number of tools. In this team there is no community , the users can just enjoy the team by installing the Frameworks , which are being used (Mozmill , Selenium).
QA Community : QA Community works to broaden our community outreach and build a legion of community testers that will continue to help improve the Firefox browsing experience for users all over the world. Although the goal of this team seems very interesting and usefull , untill now Community Contribution is not available.
From my point of view Mozilla do provide a high quality and efficient QA. Each team fill the goals and do participate in the whole project. An example of high quality assurance is the Mozilla Firefox , which i do use it the last 5 years. The reason is that provides the following issues :
b) Many ways to report a bug
c) Extensions and add-ons developed by the community and the teams
Finally it’s a truth that after the presentation during the class i did understood the real reasons why i still use Mozilla Firefox…