Firefox 11 Sprint #1

The following is a sprint to burn down bug fix verifications ahead of the release of Firefox 11 on March 13, 2012.

Status - 0 / 85 bugs verified (2012-02-27)

DISCLAIMER

Some of the bugs are security bugs requiring elevated access. For the most part, being cc'd on the bug will grant you enough access to do the testing. Please contact Anthony Hughes if you want to help.

Participants

If you wish to participate, please add your name below and contact Anthony Hughes.

• juanb
• jsmith

What to Do

Finding a Bug

• Open up the following list of Bugs
• Pick a bug that you think you are able to test

Asking for Help

There are several ways you can ask for help:

• comment in the bug and ask for assistance reproducing the bug
• indicate what you have done so far in an attempt to reproduce the bug
• sign onto #qa channel on irc.mozilla.org and ask for help verifying the fix, include the bug number
• if all else fails, contact Anthony Hughes by email or on IRC (username: ashughes)

Testing a Bug

• Read through the bug to identify the test you need to perform; things to look for:
  • steps to reproduce
  • affected versions of Firefox
  • affected operating systems
  • installed add-ons, plug-ins, third-party software
• Test the bug on the affected version to make sure you can reproduce the bug
  • If not, move on to another bug
• Once you confirm you can reproduce the bug, test the bug on the latest Beta
  • When you can reproduce the bug on an affected build but not the latest Beta, confirm the fix
  • When you can reproduce the bug on an affected build AND the latest Beta, you may need to reopen the bug

Confirming a Fix

Comment in the bug that you verify the bug is fixed, including the following information

• Firefox version(s) tested
• Operating system(s) tested
• Steps you took to test the fix
• NOTE: a bug which affects ALL platforms should be tested on at least Windows 7, Mac OSX 10.6, and Ubuntu 11.10

Example:

Verified fixed on Firefox 11.0b4 in Windows 7 64-bit
using the steps from comment 0

You will also need to edit the following fields:

• status-firefox11 flag should be set to verified
• if the bug affects multiple Firefox versions, change the [qa+] whiteboard tag to [qa+][qa!:11]
• if the bug only affects Firefox 11, change the [qa+] whiteboard tag to [qa!]
• NOTE: if you don't have access, ask someone to update the fields for you

Reopening a Bug

Comment in the bug that you can still reproduce the bug, including the following information

• Firefox version(s) tested
• Operating system(s) tested
• Steps you took to test the fix
• Ask if this qualifies the bug to be reopened

Example:

I can still reproduce this bug on Firefox 11.0b4 in Windows 7 64-bit
using the steps from comment 0.

Should I reopen this bug?

You can move on to another bug after doing so, a developer or project manager will respond to the request.