Quality Assurance
Contents |
Overview
Quality Assurance is a combined set of efforts driven toward ensuring that products keep the quality set by their brand. In case of Mozilla QA is a central efforts that guarantees Firefox browser quality, Thunderbird email client quality and many others. So whenever you think of how stable, secure, reliable and solid Firefox is, think of the huge community of people who're working on top of the developers, user interface artists and product architects to ensure the best quality possible. And whenever you think something does not work as it should, consider joining our QA community and helping us identify the problems and prepare them for the developers to fix.
Mozilla has many different systems for ensuring QA. They differ in complexity, scale, target and form. Examples can be a complex automated test set launched every hour to test what has changed and if the product still works as designed after the change, to such simple ones as uninstall form data that gathers information from users who uninstalled Firefox about the reasons they did so.
Elements
- Litmus
- Uninstall survey data
- Hendrix
Glossary
- Bug
- Regression
- UI
- Test
- Feedback
Bug system
No matter what you do around QA, once you identify a problem, you need to report it so that developers and module owners/peers can work on it.
You can also see a list of bugs where people request support from QA.
Mozilla is using a tool named Bugzilla as a central place of operations. It means that virtually all tasks, requests, problems and features are triaged through Bugzilla system. Every single task (be it a problem with a wrong icon in an alert window) is identified as a single bug reported in Bugzilla system.
To learn how to use Bugzilla, please use our handy Bugzilla:Tutorial.