QA/Tracking Bugs
< QA
Jump to navigation
Jump to search
How to Track Relevant Incoming Bugs
- In Mozilla, a QA must not only test and then file their own bugs, but must also help harness the incoming flood of community bugs for valid problems.
- Creating Search Queries on Bugzilla
- The tool that Mozilla uses to keep track of bugs is Bugzilla. Bugzilla offers a couple of ways for a user to find bugs on its database. There is a simple search option and an advanced search option. Each one offers a unique way of searching that allows the user some flexibility in how they want to perform their search. A simple search will only restrict search parameters to any currently not-fixed bug that match the string inputted by the user. Meanwhile, the advanced search form allows the user the ability to really cut down on any glut found through a simple search. With that said, it can be a bit confusing. So, Bugzilla offers a "Give me Some Help" hyperlink located in the top left portion of the form that reloads the page with hover-enabled tool-tips to guide you through each module.
- Persistent Queries and how to Manage them
- After creating a query, you might want to keep that query for future use. If that's the case, it can be transitioned into a Saved Search, which will appear in the page footer. To save a search, scroll to the bottom of the page, fill out the [image_link_here text field] at the bottom of the page and click on the "Remember Search" button.
- It's very useful if you only plan to go through the bugs every so often, or if you need to track something based on keywords or fields other than product/component, or when you need to look through older bugs.
- Tracking Components
- If you want something more immediate, you can choose to track a component, such as Disability Access. This is possible via your Bugzilla preferences. Make sure to track the relevant component in both Core->Disability Access APIs and in the products you care about, such as Firefox (Firefox->Disability Access) or Thunderbird.