Mobile/Testdrivers Program/How To/File a Bug: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 1: Line 1:
These instructions are meant to help you file a bug that's actionable for engineering.
These instructions are meant to help you file a bug that's actionable for engineering.
== Create a Bugzilla Account ==
* If you don't have a Bugzilla account, go to the '''[https://bugzilla.mozilla.org/createaccount.cgi sign-up page]''' and check out [https://secure.flickr.com/photos/28345864@N07/6354711101/in/set-72157628028362765 the image steps] if necessary (keep clicking Next-->).
* Use the same email you signed up for the Test Drivers Program with, if possible.


== Did Firefox Crash? ==
== Did Firefox Crash? ==

Revision as of 21:04, 4 May 2012

These instructions are meant to help you file a bug that's actionable for engineering.

Create a Bugzilla Account

  • If you don't have a Bugzilla account, go to the sign-up page and check out the image steps if necessary (keep clicking Next-->).
  • Use the same email you signed up for the Test Drivers Program with, if possible.

Did Firefox Crash?

Try to get the crash ID, see these image steps (keep clicking Next-->) ==

  • The last step in the instructions is to grab the "Crash Report ID", put this in a safe place and add it to the bug you file below

Step 3. Click here, log in if necessary, and then fill out the form

  • Hopefully you have the log in a file, and you can attach it to the bug. Please take the time to write:
    • An accurate summary of your issue. “Aurora crashes when trying to load an image on http://facebook.com” is way more useful than “Facebook doesn't work”
    • A description that explains what you see, what you expected to see, and any other pertinent information
    • Steps to reproduce. If you can take a reproducible sequence of actions to cause a bug to manifest, we will be really grateful, and the bug is much more likely to be fixed than one we have to guess at
    • A description of your device and the version of Fennec you're using. Something like “Samsung Galaxy S2, Android 2.3.4, Nightly build from 2012-05-04” is enough. You can find out your Android version in the Settings application.
  • You can ignore everything but the "Summary" (bug title) and "Description".
  • "Steps to reproduce" are a rough outline of how you found the problem. The more info, the better. If you don't know how you got into a situation, try to reproduce the issue. If you can't, please still file a bug!

Step 4. Attach anything you think will help

See the image steps (keep clicking Next-->).

Things to consider attaching:

  • Pictures (taken with another phone/camera) of an issue
  • Logs (if available, instructions for this coming soon)

Step 5. Watch for "bug mail", and reply if necessary

You'll sometimes get emails with a subject similar to "[Bug xxxxx] When moving the page around, the page continues to glide":

  • Please read these emails and look for any questions directed at you
  • If a reply is necessary, click the link at the top of the email and then input a reply in the text box at the bottom of the page.