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

Latest revision as of 10:13, 22 July 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

If possible, get a Log

If this is your first time visiting this page, you probably don't have the log capturing app installed already, please install it as per the instructions below and then try to reproduce your issue.

Install the free app 'aLogCat' on your device
Open aLogCat, pause the logs, go to the app's menu and "Clear" the log, then restart the log gathering
Close aLogCat and go to Aurora, do your tests or reproduce the steps that caused the issues you're seeing.
Once you've reproduced the issue(s), close Aurora and return to aLogCat where the in-app menu gives you the option to "Share" the logs gathered. Share to yourself via email or other method that gives you a way to grab the log and create a text file that you will be able to attach to a bug

If possible, take screenshots

If you are able to take screenshots of the issues, or take photos of the screen with another device, those images can also be useful to the developers and can be attached to a bug along with log files.

On Android 4.0 (Ice Cream Sandwich): hold volume down and power buttons at the same time

File the BUG report here

Following the link above to the bug report will give you a form to fill out. Here are tips on filing the actual bug report:

Hopefully you have the log file (text file containing logs grabbed in the log capture instructions, and you can attach it and any screenshots 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!

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.

@@ Line 1: / Line 1: @@
 These instructions are meant to help you file a bug that's actionable for engineering.
-== Step 1. Check the [https://wiki.mozilla.org/Mobile/Testdrivers_Program/How_To/File_a_Bug/KnownIssuesList Known Issues list] to make sure your bug isn't known  ==
+== 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.
-<br>
+== Did Firefox Crash? ==
+Try to get the crash ID, see [https://secure.flickr.com/photos/28345864@N07/6380074109/in/set-72157628089235789 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 2. Make sure you have a Bugzilla account by [https://bugzilla.mozilla.org/createaccount.cgi?GoAheadAndLogIn=1 logging in] ==
+== If possible, get a Log ==
-If you don't have a Bugzilla account, check out [http://LINK_NEEDED the image steps] of how to sign up (keep clicking Next-->) .
+If this is your first time visiting this page, you probably don't have the log capturing app installed already, please install it as per the instructions below and then try to reproduce your issue.
+* Install the free app 'aLogCat' on your device
+* Open aLogCat, pause the logs, go to the app's menu and "Clear" the log, then restart the log gathering
+* Close aLogCat and go to Aurora, do your tests or reproduce the steps that caused the issues you're seeing.
+* Once you've reproduced the issue(s), close Aurora and return to aLogCat where the in-app menu gives you the option to "Share" the logs gathered.  Share to yourself via email or other method that gives you a way to grab the log and create a text file that you will be able to attach to a bug
-== Step 3. [https://bugzilla.mozilla.org/enter_bug.cgi?product=Fennec%20Native&component=General&comment=Steps%20to%20reproduce:%0D%0A1.%20%0D%0A2.%20%0D%0A3.%20%0D%0A%0D%0AWhat%20you%20expected: Click here], log in if necessary, and then fill out the form ==
+== If possible, take screenshots ==
-* You can ignore everything but the "Summary" (bug title) and "Description".
+If you are able to take screenshots of the issues, or take photos of the screen with another device, those images can also be useful to the developers and can be attached to a bug along with log files.
-* Appropriate bug titles would be "When moving the page around, the page continues to glide" or "Hitting the back button does nothing after surfing for a while"
-* "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 ==
+On Android 4.0 (Ice Cream Sandwich): hold volume down and power buttons at the same time
-<br>
-== Step 5. Watch for "bug mail", and reply if necessary ==
+== File the [https://bugzilla.mozilla.org/enter_bug.cgi?product=Fennec&component=General&status_whiteboard=%5BMTD%5D&op_sys=Android&comment=Web%20page%20or%20screen%20you%20were%20on%20when%20you%20saw%20the%20issue:%20%0D%0A%0D%0ASteps%20to%20reproduce:%0D%0A1.%20%0D%0A2.%20%0D%0A3.%20%0D%0A%0D%0AWhat%20you%20expected:%20%0D%0A%0D%0ACrash%20report%20ID%20%28if%20applicable%29:%20 BUG report here] ==
-<br>
+Following the link above to the bug report will give you a form to fill out.  Here are tips on filing the actual bug report:
+Hopefully you have the log file (text file containing logs grabbed in the [[#If_possible.2C_get_a_Log|log capture instructions]], and you can attach it and any screenshots 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'''!
+== 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.