The Mozilla Quality Assurance (QA) team drives software quality assurance activities across Mozilla and plays a key role in releasing a diverse range of software products on schedule. Within each project in Mozilla, we work to explore new features, write and execute tests, uncover and file bugs, build and maintain tools, collect and analyze metrics, and support the release world-class products that promote the open Web.
Here you'll find articles and tools to help you gear up to join the QA team testing Firefox to ensure that each release is as good as it can be.
- How can I help test?
There are lots of ways for you to become a community contributor to the Mozilla quality team.
Get started with Matrix, the primary form of communication for members of the Mozilla community.
- All Mozilla projects use Bugzilla to track bugs. You will need to create an account with Bugzilla in order to report bugs and triage them.
- Bug writing guidelines
- The more effectively a bug is reported, the more likely that an engineer will actually fix it. By following these guidelines, you can help ensure that your bugs stay at the top of the Mozilla engineers' heap, and get fixed.
- A Bug's Life
- This tutorial will give an overview of what happens in the states that a bug will go through as well as how it will go from one to the next within its total life. It also explains the meaning of flags/keywords used in QA.
- Filing Crash Bugs
- This document lists guidelines and tips on how to file bug reports for crashes in a way that helps in debugging and fixing the reported issue.
- Confirming unconfirmed bugs
- Identify useful bug reports and close the rest.
- Triaging Bugs for Firefox
- Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproducing bugs.
- Screening duplicate bugs
- Help get bugs fixed faster by screening incoming reports for duplicates.
- General Guidelines
- What to do and what not to do in Bugzilla.
- Manual Test Case Writing Primer
- How to write proper manual test cases
- Automated testing at Mozilla
- Documentation about creating and using automated tests for Mozilla code.
- Running automated tests
This page lists the steps required to run Mozilla's automated test suites.
- Developing tests
- Ensure that future changes to Mozilla don't break things that currently work correctly.
- Avoiding intermittent test failures
- Suggestions for ways to make your tests more reliable, thereby helping to avoid random, intermittent test failures.
- Test Verification
- When a changeset adds a new test, or modifies an existing test, the test verification (TV) test suite performs additional testing to help find intermittent failures in the modified test as quickly as possible.
- Mozharness FAQ
- Answers to common questions about Mozharness.
- Robocop is the automated testing system used for Firefox for Android. Learn its code style guidelines
- Get started with Marionette UI testing.
- Learn how to use the industry standard, cross-browser, cross-platform Web runtime testing system from the W3C used by Mozilla and others to ensure browser interoperability.
- External Media Tests
- Get started testing HTML5-based video elements using VideoPuppeteer, a Marionette- -based test suite used to test sites like YouTube and Netflix.
- Chrome tests
- A chrome test is basically a Mochitest running with chrome privileges.
- Triaging Bugs for Firefox
- Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproduce a bug.
- Tips and Tricks
- These tips and tricks will make your life easier when you are testing.
- Every 24 hours, a "nightly" build is created that testers all over the world download and test, reporting as they go along on any bugs that hit them.
- Command Line Options
- Command line options are used to specify various startup options for Firefox.
- Reporting a Performance Problem
- This article will guide you in reporting a performance problem using the Gecko Profiler extension.
- Crash reporting
- Firefox ships with an open-source crash reporting system.
- Logging with the Android Debug Bridge and Logcat
- This article will provide a walkthrough in downloading and setting up an environment to which one can gain access to and view Android system logs.
- Enabling the Error Console
- See the Mozilla Hacks article on Remote Debugging on Firefox for Android for web content. If you need to debug the Firefox browser itself use Android's adb logcat.
- Simulator vs Emulator vs Device
- These are three basic options when it comes to getting a Firefox OS environment in order to work on, or developing for, Firefox OS.
- Discover the different tools at your disposal to debug your Firefox OS code.
- Reporting Bugs
- This article provides a guide to filing bugs against the Firefox OS project, including Gaia and B2G.
- Automated Testing
- Learn various aspects of testing Firefox OS, including running different tests, automation, and result reporting and tracking.
- Gaia Performance Tests
- This article provides information about running performance tests on Gaia, as well as how to create new tests.
- Feature Support Chart
- There are several different builds of Firefox OS you can download or build for yourself, and there are some differences between the types of features available on each device.
- Reducing testcases
- Improve bug reports by turning broken web pages into simple testcases, which can help developers understand the bug and can also be used for creating automated tests.
- Managing XFails
- One of the ongoing tasks of the Web QA department is managing xfails. This document will explain what xfails are, and describe the steps one can take to investigate and update them.
- Running Automated Tests
- So you’re interested in contributing to Mozilla Web QA automation projects but don’t know where to start? This doc will help you get up and running a set of tests locally.