QA/Community/Bug Day/Feb 11 2010

From MozillaWiki
< QA‎ | Community‎ | Bug Day
Jump to: navigation, search

Please join Mozilla QA for a qawanted Bugday on Feb. 11, 2010 (9:00am PST - 3:00pm PST)


  • Teach the Mozillla QA Community how to find and address bugs with "qawanted" keyword requests
  • As a community, significantly reduce the number of open "qawanted" requests

How to get involved

  • Join #bugday (Say hello, tell us you're there to help)
  • Be ready to be handed a bug to investigate. Even if you have no idea what to do, someone will walk you through the process, if you need it.

What to do

"qawanted" is a keyword that gets added by someone that is looking for some sort of help in a bug. It can be anything from finding a regression range to making a simplified test case to finding more reliable steps to reproduce the bug. Here is the list of bugs we'll be working on for this bugday:

Confirmed bugs with qawanted keyword

It is a list of confirmed Firefox bugs for 3.5, 3.6 or trunk. So you'll have to let us know if we give you a bug that you don't have a version of. That also applies to OS specific bugs.

The list isn't very long. However, each one can be different and it may not always be apparent what is being asked for. So here are some helpful tips to get you headed in the right direction.

  • First determine what the request was for and if it's already be addressed or not
    • Open the bug, read the inital comments to get an idea what the bug is about. Then jump to the bugs "History" (in the upper right corner of the bug content, next to the Modified date). Find the entry where the qawanted keyword was added. Then cross reference that poster and date/time with a comment in the bug. That should lead you to the request.
      • Unfortunately, not all qawanted requests come with a description of what is needed. In that case, remove the qawanted keyword, ask for what is needed with a comment and ask they put the keyword back when a better request is filed.
    • Once you've found the request, determine it has been addressed or not by reading through the comments.
      • If the qawanted work has been done, simply remove the keyword and move on. (yep, sometimes the keyword is not removed once the issue has been addressed.
      • If the work has not been done, this is where the fun begins.
  • Do your best to address the qawanted request. Solve whatever issue is at hand, every bug is different so this is where your QA skills come into play. If you can't figure out what to do or just need some guidance, please feel free ping us in #bugday and we'll help you accordingly.

See you in #bugday,


Mozilla QA

Bugday Stats

  • Starting bug count - 32
  • Ending bug count - 10 (69% reduction)
    • (goal: at least a 50% reduction in qawanted requests from this list)
  • Active Participants 5
    • Community - 2 (5 bugs)
    • Moz QA - 3 (17 bugs)
  • Actions taken:
    • provided the qawanted requested information - 4 bugs
    • resolved as WFM - 3 bugs
    • where previous action had been taken but the keyword not removed - 8 bugs
    • asked for a clearer request - 4 bugs
    • asked for reporter help - 1 bug
    • removed keyword because request was actually regressionwindow-wanted - 2 bugs