: New feature! MozillaWiki is now mobile-friendly. Visit from a mobile device to see new mobile theme + try editing. Release details.

Bugdays/Bug-Triage

From MozillaWiki
Jump to: navigation, search

Bug Triage Day

Why?

Bugs can stay unnoticed in Bugzilla for a long period of time – they’re either not moved in the right component or are missing vital information to get them in developers’ hands. Our aim for the day is to manage incoming bugs in the Untriaged component.

What is “triaging”?

Managing incoming bugs: move them in the right component, asking for more information if necessary, changing the state of bugs accordingly, ensuring that bugs have all required information.

This event is open to everyone wanting to help make Firefox better. We usually advertise it on QMO and IRC every week, so you don't miss any updates.

Details

  • Where: IRC #qa channel
  • When: Every Monday, all day long, but you can contribute any other time you wish.

Pre-requisites

Bugzilla

Bugzilla is Mozilla's bug tracking system. This is where bugs are reported and where every change for a bug is stored and tracked.

To update a bug report in any way, you will need to sign in to Bugzilla using a Bugzilla account or Mozilla Persona. If you don't already have an account, you can sign up here.

Optional

These accounts are not necessary to participate in a bug day, but they're useful to create as you begin to contribute to Mozilla projects!

Mozilla Persona

Persona is a service developed by Mozilla which enables secure access to various services using nothing more than your email address and password. You can start using Persona for Bugzilla by clicking Sign in to Persona (blue "Sign in" arrow) here.

The Persona account can also be used for signing in to other Mozilla sites (e.g. Moztrap, Mozillians).

Mozillians

Mozillians is a network of our contributors. You might want to join it in order to connect with other contributors regarding community events, contribution opportunities, knowledge sharing and so on.

If you have any questions regarding the above or this event, please address them on the IRC #qa channel.

How to Triage bugs

Here is a basic set of instructions to help you triage a bug
  • Install the latest Firefox Nightly to triage the bugs on it.
  • Pick a bug from THIS LIST.
  • We suggest that you check that you are confirming a bug on a relevant platform. You can sort the bugs by operating system, by clicking on the column header.
  • Read the description and comments in the bug to understand the problem.
  • If you clearly understand the bug, move it out of the Untriaged component into something more appropriate.
  • If you don't understand the bug or can't reproduce it, add a comment to the report asking followup questions. Some questions you might want to ask:
    • Does the bug happen with the latest Nightly?
    • Does the bug happen when running in Safe Mode?
    • Does the bug happen in competing browsers?
    • Does the bug happen on other Firefox versions?
    • What are the detailed steps to reproduce?
    • Is there a minimized testcase or URL we can use to test?
  • If you can reproduce the bug, mark it as NEW.
  • Getting started: Tutorial
Notes
  • Migrate Bugs to SUMO if its a support question, not a bug.
  • You might also find the following articles useful: bugmasters guide, MDN guide.
  • Make sure to add [bugday-yyyymmdd] in the QA Whiteboard (or the normal Whiteboard, if the QA Whiteboard is not available) of all the bugs you work on today. That way you will mark the fact that you contributed to this event.
    • If you don’t have the rights to edit the QA Whiteboard, you can simply add [bugday-yyyymmdd] in a comment.

Hosting a test day

Anyone is welcome to host a bugday or test day focused in an area of interest.

If you're hosting a test day or bug day, please report on its results!

  • Email about the results on the dev-quality mailing list.
  • Record the participants (including organizers and moderators) here: https://adhoctribution.herokuapp.com/
  • Follow up in QA or community meetings to thank all the testers. :)

Results

Many thanks to everyone that contributed to these events!

2015

Q3

Q2

Q1

2014

Q4

Q3

Q2


See Also