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

no edit summary
No edit summary
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.


== 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  ==
== Step 1. '''If Firefox Crashed''', 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", which you'll put in the bug you file
 
== Step 2. 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  ==


<br>
<br>


== Step 2. Make sure you have a Bugzilla account by [https://bugzilla.mozilla.org/createaccount.cgi?GoAheadAndLogIn=1 logging in] ==
== Step 3. Make sure you have a Bugzilla account by [https://bugzilla.mozilla.org/createaccount.cgi?GoAheadAndLogIn=1 logging in] ==
* 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-->).
* 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.
* Use the same email you signed up for the Test Drivers Program with, if possible.


== Step 3. [https://bugzilla.mozilla.org/enter_bug.cgi?product=Fennec%20Native&component=General&comment=Web%20page%20or%20screen%20you%20were%20on%20when%20you%20saw%20the%20issue:%20%0D%0A%0D%0ASteps%20to%20reproduce:%20%0D%0A1.%20%0D%0A2.%20%0D%0A3.%20%0D%0A%0D%0AWhat%20you%20expected:%0D%0A%0D%0ACrash%20report%20ID%20%28if%20applicable%29:%20 Click here], log in if necessary, and then fill out the form ==
== Step 4. [https://bugzilla.mozilla.org/enter_bug.cgi?product=Fennec%20Native&component=General&comment=Web%20page%20or%20screen%20you%20were%20on%20when%20you%20saw%20the%20issue:%20%0D%0A%0D%0ASteps%20to%20reproduce:%20%0D%0A1.%20%0D%0A2.%20%0D%0A3.%20%0D%0A%0D%0AWhat%20you%20expected:%0D%0A%0D%0ACrash%20report%20ID%20%28if%20applicable%29:%20 Click here], log in if necessary, and then fill out the form ==
* You can ignore everything but the "Summary" (bug title) and "Description".
* You can ignore everything but the "Summary" (bug title) and "Description".
* 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"
* 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'''!
* "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 ==
== Step 5. Attach anything you think will help ==
See the [https://secure.flickr.com/photos/28345864@N07/6354756591/in/set-72157628028447421 image steps] (keep clicking Next-->).
See the [https://secure.flickr.com/photos/28345864@N07/6354756591/in/set-72157628028447421 image steps] (keep clicking Next-->).


Line 21: Line 24:
* Logs (if available, instructions for this soon)  
* Logs (if available, instructions for this soon)  


== Step 5. Watch for "bug mail", and reply if necessary ==
== Step 6. 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":
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
* 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.
* 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.
Confirmed users
1,798

edits