QA/Bug Triage Guidelines: Difference between revisions

Jump to navigation Jump to search

QA/Bug Triage Guidelines (view source)

Revision as of 14:15, 24 May 2016

123 bytes removed ,  24 May 2016
no edit summary
No edit summary
No edit summary
Line 29: Line 29:
= Components, Contacts and Suggested Comments=  
= Components, Contacts and Suggested Comments=  
== Bugzilla Component Ownership ==
== Bugzilla Component Ownership ==
You can find a list with Bugzilla component ownership for bug decision [https://docs.google.com/spreadsheets/d/10i30CFUPJM7snz0xX3czFJeBh2tNwjwjtI409DQw3x0/edit?pref=2&pli=1#gid=1391890455/ here]
You can find a list of Bugzilla component ownership for bug decision [https://docs.google.com/spreadsheets/d/10i30CFUPJM7snz0xX3czFJeBh2tNwjwjtI409DQw3x0/edit?pref=2&pli=1#gid=1391890455/ here]


== Bug Triage Component Selection: Firefox & CORE ==
== Bug Triage Component Selection: Firefox & CORE ==
Line 44: Line 44:
| mhoye || Mike Hoye || Ping Mike for bugs where the Reporter may be difficult and he will take a look into the issue
| mhoye || Mike Hoye || Ping Mike for bugs where the Reporter may be difficult and he will take a look into the issue
|-
|-
| emceeaich || Emma Humphries || Bug Master - Notify Emma if there are items with keywork "Crash" if there has been not activity by Mozilla
| emceeaich || Emma Humphries || Bug Master - Notify Emma if there are items with keyword "Crash" if there has been not activity by Mozilla
|-
|-
| RyanVM || Ryan VanderMeulen || Clearly mark bug with comments when we need to discuss an issue with Ryan
| RyanVM || Ryan VanderMeulen || Clearly mark bug with comments when they later on need to be discussed with Ryan
|}
|}


Line 57: Line 57:
| Component || Where a Component is set to something other than Untriaged, leave the bug alone unless asked to do MozRegression or QAWanted
| Component || Where a Component is set to something other than Untriaged, leave the bug alone unless asked to do MozRegression or QAWanted
|-
|-
| Untriaged vs. Unconfirmed || The goal is to reduce the Untriaged issues number, Ryan is not concerned with # of Unconfirmed. The end goal is to have all items placed in an appropriate component. If further confirmation is needed you will be asked
| Untriaged vs. Unconfirmed || The goal is to reduce the Untriaged issues number, by placing them under the correct component.  
|-
|-
| New || Where there is no Component, set one. Where it cannot be reproduced, ask the Reporter for additional information or close as Incomplete / WFM
| New || Where there is no Component, set one. Where it cannot be reproduced, ask the Reporter for additional information or close as Incomplete / WFM
'''NOTE''': Sometimes, reporters mark issues as New without being confirmed by an Mozillian or Community Member. Read carefully to see if it needs confirmation to remain New or it needs to be changed back to Unconfirmed until it can be reproduced
'''NOTE''': Sometimes, reporters mark issues as New without being confirmed by a Mozillian or Community Member. Read carefully to see if it needs confirmation to remain New or it needs to be changed back to Unconfirmed until it can be reproduced
|-
|-
| Crash || If there is no activity by Mozilla, ping or email Emma (:emceeaich) so that she can get someone to look into the issue. place the crash tag also.
| Crash || If there is no activity by Mozilla, ping or email Emma (:emceeaich) so that she can get someone to look into the issue. Place the crash tag also.
|-
|-
| Mozilla Communications || When there is a lot of Mozilla Communications within the bug, ping a developer on IRC and ask them to set the appropriate component
| Mozilla Communication || When there is a lot of Mozilla Communication within the bug, ping a developer on IRC and ask him to set the appropriate component
|-
|-
| Close Me <date> || Apply at your comfort, there is not standard. If you apply, please give the reporter a chance to respond (at least 30 days)
| Close Me <date> || Apply at your comfort, there is no standard. If you apply it, please give the reporter a chance to respond (at least 30 days)
|-
|-
| Enhancement & Feature Requests || Enhancements and Feature Request should have an appropriate Component assigned. The developers and PM in that component will decide if it will be implemented or marked as Resolved-Won't Fix
| Enhancement & Feature Requests || Enhancements and Feature Requests should have an appropriate Component assigned. The developers and PM in that component will decide if it will be implemented or marked as Resolved-Won't Fix
'''NOTE''': If you are sure that a Feature Request or an Enhancement is a valid one, you could also set his status to NEW, but usually this is the component's owner job.
'''NOTE''': If you are sure that a Feature Request or an Enhancement is a valid one, you could also set its status to NEW, but usually this is the component owner's job.
|-
|-
| Context || Bugs that contain sensitive information or that may be harmful to the testers should be marked Context. These items can be reviewed with Ryan or Emma
| Context || Bugs that contain sensitive information or that may be harmful to the testers should be marked Context. These items can be reviewed with Ryan or Emma
Line 98: Line 98:




2.Considering the fact that I cannot reproduce this and the fact that the reporter did not answered to my/<name> request until now, I will mark this as Resolved-Worksforme.
2.Considering the fact that I cannot reproduce this and the fact that the reporter did not answered to my/<name> request until now, I will mark this as Resolved - Worksforme.


If anyone can still reproduce it, feel free to reopen the issue and provide more information.
If anyone can still reproduce it, feel free to reopen the issue and provide more information.
Line 112: Line 112:
There are no crash reports in the last 7/14/28 days in the crash signatures provided, therefore closing this bug as Resolved: Works for me. Please reopen the bug if the crash still reproduces and provide more information.
There are no crash reports in the last 7/14/28 days in the crash signatures provided, therefore closing this bug as Resolved: Works for me. Please reopen the bug if the crash still reproduces and provide more information.
|-
|-
| MozRegression: When we ask a user to use mozregression || Given the fact that the issue seems to be related to something that is specific to your setup, could you please try to find a regression range using Mozregression tool?
| MozRegression: When we ask a user to use MozRegression || Given the fact that the issue seems to be related to something that is specific to your setup, could you please try to find a regression range using MozRegression tool?
Information on the tool is available at http://mozilla.github.io/mozregression/. Please don't hesitate to contact us if you encounter any problems.
Information on the tool is available at http://mozilla.github.io/mozregression/. Please don't hesitate to contact us if you encounter any problems.
|-
|-
Line 138: Line 138:


|-
|-
| Using Mozzregression Tool on Mac OS || If you need to find when an issue was introduced (regression), the easiest and best way to do this is by using the Mozregression tool.  
| Using MozRegression Tool on Mac OS || If you need to find when an issue was introduced (regression), the easiest and best way to do this is by using the MozRegression tool.  


In order to do this, you'll need to install a couple of things before starting the tool. Here are the steps needed depending on OS needed for testing:
In order to do this, you'll need to install a couple of things before starting the tool. Here are the steps needed depending on OS needed for testing:
Line 144: Line 144:
         • Mac OS X (10.11 only, for older versions see next bullet)
         • Mac OS X (10.11 only, for older versions see next bullet)


In order to use Mozregression tool on Mac OS X 10.11, you will need to perform some additional steps than on other Mac OS versions. One of the steps is installing a virtual environment trough python so you won't get any conflicts between python and Mozregression.
In order to use MozRegression tool on Mac OS X 10.11, you will need to perform some additional steps than on other Mac OS versions. One of the steps is installing a virtual environment trough python so you won't get any conflicts between python and MozRegression.


Here are the complete steps to install and use Mozregression trough Virtual environment:
Here are the complete steps to install and use MozRegression trough Virtual environment:


1. First, you will need to open a Terminal window and enter the following command "sudo su" (without quotes). You will be prompted to insert the PC user password (the password used for logging in on the Mac OS user). If you don't see the characters you are entering, don't worry, they are entered but due to security are hidden. After entering them press the "Enter" key.<br>
1. First, you will need to open a Terminal window and enter the following command "sudo su" (without quotes). You will be prompted to insert the PC user password (the password used for logging in on the Mac OS user). If you don't see the characters you are entering, don't worry, they are entered but due to security are hidden. After entering them press the "Enter" key.<br>
Line 166: Line 166:
3. After the Python installation is finalized, you'll need to install the latest version of mozregression by entering the next command "sudo pip2 install -U mozregression"<br>
3. After the Python installation is finalized, you'll need to install the latest version of mozregression by entering the next command "sudo pip2 install -U mozregression"<br>
4. After doing this you are ready to start digging into builds. You can do that by using the next two commands "mozregression --good <build_date>" (eg: mozregression --good 2014-12-31) when you only know the build when it was ok, or "mozregression --good <build_date> --bad <build_date>" (eg: mozregression --good 2014-12-31 --bad 2015-12-31) when you know both a good build and a bad build.<br>
4. After doing this you are ready to start digging into builds. You can do that by using the next two commands "mozregression --good <build_date>" (eg: mozregression --good 2014-12-31) when you only know the build when it was ok, or "mozregression --good <build_date> --bad <build_date>" (eg: mozregression --good 2014-12-31 --bad 2015-12-31) when you know both a good build and a bad build.<br>
5. Mozregression will start downloading builds and open them to test your issue. After testing the issue you must validate the build with "good" or "bad". The tool will continue to download and open builds until the search is narrowed down to two builds and will throw a "Pushlog link" that you will need to provide in the bug comment together with any additional informations that we consider to be helpful.<br>
5. MozRegression will start downloading builds and open them to test your issue. After testing the issue you must validate the build with "good" or "bad". The tool will continue to download and open builds until the search is narrowed down to two builds and will throw a "Pushlog link" that you will need to provide in the bug comment together with any additional information that we consider to be helpful.<br>


If something has been missed you can find all the mentioned information also at this link -> http://mozilla.github.io/mozregression/quickstart.html.  
If something has been missed you can find all the mentioned information also at this link -> http://mozilla.github.io/mozregression/quickstart.html.  


'''NOTE''': Mozregression tool is not perfect and will throw some errors on some old builds. If it is your case, please refer to my other lesson from above this where you have information on how to manually create the "Pushlog link" for the found builds.
'''NOTE''': MozRegression tool is not perfect and will throw some errors on some old builds. If it is your case, please refer to my other lesson from above this where you have information on how to manually create the "Pushlog link" for the found builds.


If you encounter some errors involving Python while trying to use mozregression on Mac OS, please look at the next lesson to resolve this issue.
If you encounter some errors involving Python while trying to use MozRegression on Mac OS, please look at the next lesson to resolve this issue.
|-
|-
| Instaling virtual Environment for Mozregression to work on Mac OS || It seams that now days, not only the Mac OS 10.11 has some conflicts between python and mozregression when trying to do a regression window. In order to resolve this conflicts, you will need to install and use mozregression trough a virtual environment. Here are the steps you need to follow in order to do that:
| Instaling virtual Environment for MozRegression to work on Mac OS || It seams that nowadays, not only the Mac OS 10.11 has some conflicts between python and MozRegression when trying to do a regression window. In order to resolve these conflicts, you will need to install and use MozRegression trough a virtual environment. Here are the steps you need to follow in order to do that:


1. First, you will need to open a Terminal window and enter the following command "sudo su" (without quotes). You will be prompted to insert the PC user password (the password used for logging in on the Mac OS user). If you don't see the characters you are entering, don't worry, they are entered but due to security are hidden. After entering them press the "Enter" key.<br>
1. First, you will need to open a Terminal window and enter the following command "sudo su" (without quotes). You will be prompted to insert the PC user password (the password used for logging in on the Mac OS user). If you don't see the characters you are entering, don't worry, they are entered but due to security are hidden. After entering them press the "Enter" key.<br>
Line 186: Line 186:
9. '''REMEMBER''' ! The environment must be activated each time when you want to use the Mozregression tool.<br>
9. '''REMEMBER''' ! The environment must be activated each time when you want to use the Mozregression tool.<br>
|-
|-
| Using Mozzregression Tool on Windows || On Windows platform you can either use the Mozregression gui from github releases page, or you can use the tool trough command line as on Mac OS. In the next steps I will present the command line way on Windows.
| Using MozRegression Tool on Windows || On Windows platform you can either use the MozRegression gui from github releases page, or you can use the tool trough command line as on Mac OS. In the next steps I will present the command line way on Windows.


1. First, you will need to download and install Python 2.7 from ActiveState website (http://www.activestate.com/activepython/downloads).<br>
1. First, you will need to download and install Python 2.7 from ActiveState website (http://www.activestate.com/activepython/downloads).<br>
2. After installing  Python you will need to open a command prompt window and enter the next command "pip install -U mozregression".<br>
2. After installing  Python you will need to open a command prompt window and enter the next command "pip install -U mozregression".<br>
3. After doing this you are ready to start digging into builds. You can do that by using the next two commands "mozregression --good <build_date>" (eg: mozregression --good 2014-12-31) when you only know the build when it was ok, or "mozregression --good <build_date> --bad <build_date>" (eg: mozregression --good 2014-12-31 --bad 2015-12-31) when you know both a good build and a bad build.<br>
3. After doing this you are ready to start digging into builds. You can do that by using the next two commands "mozregression --good <build_date>" (eg: mozregression --good 2014-12-31) when you only know the build when it was ok, or "mozregression --good <build_date> --bad <build_date>" (eg: mozregression --good 2014-12-31 --bad 2015-12-31) when you know both a good build and a bad build.<br>
4. Mozregression will start downloading builds and open them to test your issue. After testing the issue you must validate the build with "good" or "bad". The tool will continue to download and open builds until the search is narrowed down to two builds and will throw a "Pushlog link" that you will need to provide in the bug comment together with any additional informations that we consider to be helpful.<br>
4. MozRegression will start downloading builds and open them to test your issue. After testing the issue you must validate the build with "good" or "bad". The tool will continue to download and open builds until the search is narrowed down to two builds and will throw a "Pushlog link" that you will need to provide in the bug comment together with any additional information that we consider to be helpful.<br>


If I missed something you can find all the mentioned informations also at this link -> http://mozilla.github.io/mozregression/quickstart.html.  
If I missed something you can find all the mentioned information also at this link -> http://mozilla.github.io/mozregression/quickstart.html.  


'''NOTE''': Mozregression tool is not perfect and will throw some errors on some old builds. If it is your case, please refer to my other lesson from above this where you have informations on how to manually create the "Pushlog link" for the found builds.
'''NOTE''': MozRegression tool is not perfect and will throw some errors on some old builds. If it is your case, please refer to my other lesson from above this where you have informations on how to manually create the "Pushlog link" for the found builds.
|-
|-
| Using Mozzregression Tool on Linux || On Linux platform you can either use the Mozregression gui from github releases page, or you can use the tool trough command line as on Mac OS. In the next steps I will present the command line way on Linux.
| Using MozRegression Tool on Linux || On Linux platform you can either use the MozRegression GUI from github releases page, or you can use the tool trough command line as on Mac OS. In the next steps I will present the command line way on Linux.


1. First, you will need to open a Terminal window and enter the following command "sudo su" (without quotes). You will be prompted to insert the PC user password (the password used for logging in on the Linux user). If you don't see the characters you are entering, don't worry, they are entered but due to security are hidden. After entering them press the "Enter" key.<br>
1. First, you will need to open a Terminal window and enter the following command "sudo su" (without quotes). You will be prompted to insert the PC user password (the password used for logging in on the Linux user). If you don't see the characters you are entering, don't worry, they are entered but due to security are hidden. After entering them press the "Enter" key.<br>
Line 203: Line 203:
3. After the Python installation is finalized, you'll need to install the latest version of mozregression by entering the next command "sudo pip2 install -U mozregression"<br>
3. After the Python installation is finalized, you'll need to install the latest version of mozregression by entering the next command "sudo pip2 install -U mozregression"<br>
4. After doing this you are ready to start digging into builds. You can do that by using the next two commands "mozregression --good <build_date>" (eg: mozregression --good 2014-12-31) when you only know the build when it was ok, or "mozregression --good <build_date> --bad <build_date>" (eg: mozregression --good 2014-12-31 --bad 2015-12-31) when you know both a good build and a bad build.<br>
4. After doing this you are ready to start digging into builds. You can do that by using the next two commands "mozregression --good <build_date>" (eg: mozregression --good 2014-12-31) when you only know the build when it was ok, or "mozregression --good <build_date> --bad <build_date>" (eg: mozregression --good 2014-12-31 --bad 2015-12-31) when you know both a good build and a bad build.<br>
5. Mozregression will start downloading builds and open them to test your issue. After testing the issue you must validate the build with "good" or "bad". The tool will continue to download and open builds until the search is narrowed down to two builds and will throw a "Pushlog link" that you will need to provide in the bug comment together with any additional informations that we consider to be helpful.<br>
5. Mozregression will start downloading builds and open them to test your issue. After testing the issue you must validate the build with "good" or "bad". The tool will continue to download and open builds until the search is narrowed down to two builds and will throw a "Pushlog link" that you will need to provide in the bug comment together with any additional information that we consider to be helpful.<br>


If I missed something you can find all the mentioned informations also at this link -> http://mozilla.github.io/mozregression/quickstart.html.
If I missed something you can find all the mentioned information also at this link -> http://mozilla.github.io/mozregression/quickstart.html.


'''NOTE''': Mozregression tool is not perfect and will throw some errors on some old builds. If it is your case, please refer to my other lesson from above this where you have informations on how to manually create the "Pushlog link" for the found builds.
'''NOTE''': MozRegression tool is not perfect and will throw some errors on some old builds. If it is your case, please refer to my other lesson from above this where you have information on how to manually create the "Pushlog link" for the found builds.
|-
|-
| Using Mozzregression Tool with "--find-fix" attribute || If you are dealing with an issue that still reproduces on latest Firefox release build but no longer on Beta, Aurora or Nightly you can use the "--find-fix" attribute while performing regression range in mozregression. This will help you to provide information to the reporter regarding his issue. In most of the cases his issue will end up as "duplicate" or "works for me" since the problem was treated in a different bug.  
| Using MozRegression Tool with "--find-fix" attribute || If you are dealing with an issue that still reproduces on latest Firefox release build but no longer on Beta, Aurora or Nightly you can use the "--find-fix" attribute while performing regression range in mozregression. This will help you to provide information to the reporter regarding his issue. In most of the cases his issue will end up as "duplicate" or "works for me" since the problem was treated in a different bug.  


1. First, you'll need to manually find a bad Nightly build date by downloading builds from http://ftp.mozilla.org/ . For quick testing I suggest to download zip-ed builds, extract them and use the command window / terminal to launch the build with "-no-remote" and "-p" commands.  
1. First, you'll need to manually find a bad Nightly build date by downloading builds from http://ftp.mozilla.org/ . For quick testing I suggest to download zip-ed builds, extract them and use the command window / terminal to launch the build with "-no-remote" and "-p" commands.  
Line 218: Line 218:
The "--find-fix" atribute in mozregression does exactly what bisect does in normal usage. It searches for the exact push that fixed the issue. In most of the cases you end up with only one issue that you can provide to the reporter of your triaged issue as more information.
The "--find-fix" atribute in mozregression does exactly what bisect does in normal usage. It searches for the exact push that fixed the issue. In most of the cases you end up with only one issue that you can provide to the reporter of your triaged issue as more information.
|-
|-
| Using Mozzregression Tool with targeted profile for each downloaded build || Sometimes there are cases when you are unable to reproduce an issue on Mozregression downloaded builds. But if you manually download the same build and test it, you can reproduce it without problems. This could possibly happen because Mozregression has a different way of storing downloaded builds on your PC and it seams it does not uses a profile when opening the build to test. This case can be avoided by targeting a previously created profile that will be used for each downloaded build. Here are the steps to follow:
| Using MozRegression Tool with targeted profile for each downloaded build || Sometimes there are cases when you are unable to reproduce an issue on MozRegression downloaded builds. But if you manually download the same build and test it, you can reproduce it without problems. This could possibly happen because MozRegression has a different way of storing downloaded builds on your PC and it seams it does not uses a profile when opening the build to test. This case can be avoided by targeting a previously created profile that will be used for each downloaded build. Here are the steps to follow:


Windows:
Windows:
Line 237: Line 237:
The tilde character (~) refers to the current user's Home folder, so ~/Library is the /Macintosh HD/Users/<username>/Library folder. (--profile=/Users/pauloiegas/Library/Application\ Support/Firefox/Profiles/rg0ayjkt.PrintTESTn)
The tilde character (~) refers to the current user's Home folder, so ~/Library is the /Macintosh HD/Users/<username>/Library folder. (--profile=/Users/pauloiegas/Library/Application\ Support/Firefox/Profiles/rg0ayjkt.PrintTESTn)


After this steps, you are all set and can perform the regression range as normal. By using the "--profile <path>" atribute, each downloaded build trough mozregression, will use the same profile and store data on it.  
After this steps, you are all set and can perform the regression range as normal. By using the "--profile <path>" attribute, each downloaded build trough mozregression, will use the same profile and store data on it.  
This flow can be used also with "--find-fix" attribute as mentioned in the above lesson by adding it after the default command contents and the "--profile <path>" one (eg: C:\Users\paul.oiegas>mozregression --bad 2015-06-06 --good 2016-02-23 --find-fix --profile \AppData\Roaming\Mozilla\Firefox\Profiles\w9gzt0rd.testrelease2).
This flow can be used also with "--find-fix" attribute as mentioned in the above lesson by adding it after the default command contents and the "--profile <path>" one (eg: C:\Users\paul.oiegas>mozregression --bad 2015-06-06 --good 2016-02-23 --find-fix --profile \AppData\Roaming\Mozilla\Firefox\Profiles\w9gzt0rd.testrelease2).
|-
|-
| Mozregression on Android (with Windows) ||  
| MozZRegression on Android (with Windows) ||  
If you encounter a regression bug on Android OS, you will need to perform a couple of steps in order to be able to run Mozregression tool on an Android device. Here are the steps that you need to follow on Windows in order to find a regression rangel. Will update the lesson with steps also for Mac OS and Linux after I will find how to set the "Environment variables" on each of them.
If you encounter a regression bug on Android OS, you will need to perform a couple of steps in order to be able to run MozRegression tool on an Android device. Here are the steps that you need to follow on Windows in order to find a regression range. Will update the lesson with steps also for Mac OS and Linux after I will find how to set the "Environment variables" on each of them.


1. Install the latest Android SDK with Android Studio from (http://goo.gl/OPyvqU ) or only the command line tools from next link
1. Install the latest Android SDK with Android Studio from (http://goo.gl/OPyvqU ) or only the command line tools from next link
Line 257: Line 257:
- Next step would be to edit the "Path" system variable (double click on it), and add two new strings. First is "%ANDROID%\tools\" and second "%ANDROID%\platform-tools\". Hit "Ok" button for every window and you are all done with this step.<br />
- Next step would be to edit the "Path" system variable (double click on it), and add two new strings. First is "%ANDROID%\tools\" and second "%ANDROID%\platform-tools\". Hit "Ok" button for every window and you are all done with this step.<br />


5. Next you will need to install Mozregression tool by using the steps from the above lessons learned or to use the Mozregression GUI that you can download from here (https://goo.gl/DyFFok).<br />
5. Next you will need to install MozRegression tool by using the steps from the above lessons learned or to use the MozRegression GUI that you can download from here (https://goo.gl/DyFFok).<br />


6. On your Android device be sure you have the "Developer options" enabled. Tap multiple times on "Build number" area  in "About device" section of device "Settings" page. Return to device "Settings" main page and from the "Developer options" that are now displayed, switch to "On" the "USB debugging" option.<br />
6. On your Android device be sure you have the "Developer options" enabled. Tap multiple times on "Build number" area  in "About device" section of device "Settings" page. Return to device "Settings" main page and from the "Developer options" that are now displayed, switch to "On" the "USB debugging" option.<br />
Line 275: Line 275:
3. Search in installation folder/build folder for the "application.ini" file (Mac OS path is /Applications/Firefox.app/Contents/MacOS/application.ini).<br>
3. Search in installation folder/build folder for the "application.ini" file (Mac OS path is /Applications/Firefox.app/Contents/MacOS/application.ini).<br>
4. Open the ".ini" files with a text editor and search for the "SourceStamp" values.<br>
4. Open the ".ini" files with a text editor and search for the "SourceStamp" values.<br>
5. After doing this you will have to use the " http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=good_build_stamp&tochange=bad_build_stamp " link and replace the <good_build_stamp> and <bad_build_stamp> strings with the one obtained from the ini files.<br>  
5. After doing this you will have to use the " http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=good_build_stamp&tochange=bad_build_stamp " link and replace the <good_build_stamp> and <bad_build_stamp> strings with the one obtained from the .ini files.<br>  




You should verify the link obtained, and if it works and it is related with the period when the issue appeared, you should add it to the comment for the bug where regression was performed.  
You should verify the link obtained, and if it works and it is related with the period when the issue appeared, you should add it to the comment for the bug where regression was performed.  
If you have enough experience you could also point in the comment the exact push from the pushlog page that affected the build, and CC the developer that did it (if it's still available) in order to obtain th information faster. For the moment Rayan was doing this for the pushlog links I provided but we can experience this too in the future.
If you have enough experience you could also point in the comment the exact push from the pushlog page that affected the build, and CC the developer that did it (if it's still available) in order to obtain the information faster. For the moment Ryan was doing this for the pushlog links I provided but we can experience this too in the future.
|-
|-
| Performing quick Regression test by searching in build release notes || In cases when reporter mentions that in a previous version of Firefox his issue was not present and after updating it appeared, you can also do a quick manual regression by searching the problematic build release notes and observe the changes that have been made on it. To better explain this process I will refer to an Issue that I triaged, where the reported problem was an audio malfunction in an html5 game that he an his team develops, that appeared after updating from Firefox 39.0 to 40.0.
| Performing quick Regression test by searching in build release notes || In cases when reporter mentions that in a previous version of Firefox his issue was not present and after updating it appeared, you can also do a quick manual regression by searching the problematic build release notes and observe the changes that have been made on it. To better explain this process I will refer to an Issue that I triaged, where the reported problem was an audio malfunction in an html5 game that he and his team develops, that appeared after updating from Firefox 39.0 to 40.0.


In order to find the build release notes you can easily search on google for "Firefox release notes" and open the "https://www.mozilla.org/en-US/firefox/releases/" page. In this page you can view all the release notes from version 0.1 to the latest release (42.0 in the moment of writing). In my case I chose "40.0" version (https://www.mozilla.org/en-US/firefox/40.0/releasenotes/). After choosing the build, you are redirected to a page where all the major changes that entered in this build are mentioned. By looking trough the changes I observed that there were 2 changes on "html5" technology and one of them was related to "Audio Buffer". In my case the change also had a link that pointed to a page with detailed explanations and code chunks to better explain the change. This seamed that could be related a lot with the reporter problem. In my bug reply comment I mentioned the exact link of the change and asked him or his development team to look into it, since it may be the source of his problem and report any findings.
In order to find the build release notes you can easily search on google for "Firefox release notes" and open the "https://www.mozilla.org/en-US/firefox/releases/" page. In this page you can view all the release notes from version 0.1 to the latest release (42.0 in the moment of writing). In my case I chose "40.0" version (https://www.mozilla.org/en-US/firefox/40.0/releasenotes/). After choosing the build, you are redirected to a page where all the major changes that entered in this build are mentioned. By looking trough the changes I observed that there were 2 changes on "html5" technology and one of them was related to "Audio Buffer". In my case the change also had a link that pointed to a page with detailed explanations and code chunks to better explain the change. This seamed that could be related a lot with the reporter problem. In my bug reply comment I mentioned the exact link of the change and asked him or his development team to look into it, since it may be the source of his problem and report any findings.
Line 300: Line 300:
2. If it's the case: set the right component.<br>
2. If it's the case: set the right component.<br>
3. In Bugzilla, edit the tracking flags area: set as affected or unaffected the status-firefox fields for all Firefox versions (official Release, latest Beta, latest Aurora and latest Nightly).<br>
3. In Bugzilla, edit the tracking flags area: set as affected or unaffected the status-firefox fields for all Firefox versions (official Release, latest Beta, latest Aurora and latest Nightly).<br>
4. Knowing the patch that fixed the issue is an asset in getting the fix on the affected Firefox version (the mozregression tool is very helpful - ask the reporter or do it yourself).<br>
4. Knowing the patch that fixed the issue is an asset in getting the fix on the affected Firefox version (the MozRegression tool is very helpful - ask the reporter or do it yourself).<br>
|-
|-
| How to simulate bad internet connection on Mac OS || If you encounter and issue where the reporter specifies that he has a slow / bad internet connection, or you think the issue appears only when internet connection is not good enough, you can simulate this kind of environment by using a bandwidth throttling tool.
| How to simulate bad internet connection on Mac OS || If you encounter an issue where the reporter specifies that he has a slow / bad internet connection, or you think the issue appears only when internet connection is not good enough, you can simulate this kind of environment by using a bandwidth throttling tool.
Here are the steps you need to follow to install and use the tool under Mac OS:
Here are the steps you need to follow to install and use the tool under Mac OS:


Line 313: Line 313:
7. After the values are introduced, press the "OK" button to close the profiles management window and switch the tool to "ON" in order to initialize the bandwidth limitation.<br />
7. After the values are introduced, press the "OK" button to close the profiles management window and switch the tool to "ON" in order to initialize the bandwidth limitation.<br />


Please '''REMEMBER''' that in order to return to the normal interned bandwidth speed, you will always need to switch the Tool to "OFF" after testing, otherwise the limitation will remain always ON.
Please '''REMEMBER''' that in order to return to the normal internet bandwidth speed, you will always need to switch the Tool to "OFF" after testing, otherwise the limitation will remain always ON.
|-
|-
| How to simulate bad internet connection on Windows || If you encounter and issue where the reporter specifies that he has a slow / bad internet connection, or you think the issue appears only when internet connection is not good enough, you can simulate this kind of environment by using a bandwidth limiter tool.
| How to simulate bad internet connection on Windows || If you encounter an issue where the reporter specifies that he has a slow / bad internet connection, or you think the issue appears only when internet connection is not good enough, you can simulate this kind of environment by using a bandwidth limiter tool.
Here are the steps you need to follow to install and use the tool under Windows:
Here are the steps you need to follow to install and use the tool under Windows:


Line 321: Line 321:
2. Install the software and restart the computer after.<br />
2. Install the software and restart the computer after.<br />
3. After restarting, start the program and you will observe a list with all processes under windows. <br />
3. After restarting, start the program and you will observe a list with all processes under windows. <br />
4. Right click the desired process (eg: firefox) and chose to "Limit" it. A window will be displayed where you can add the desired bandwidth value for download. You can also select the value for upload by choosing "Limit" value from the dropdown related to upload.<br />
4. Right click the desired process (eg: firefox) and chose to "Limit" it. A window will be displayed where you can add the desired bandwidth value for download. You can also select the value for upload by choosing "Limit" value from the drop-down related to upload.<br />
5. Confirm the settings and you are all done. In order to properly limit the process you desire, be sure you choose the one that consumes bandwidth while navigating trough websites / listening to videos in the browser.<br />
5. Confirm the settings and you are all done. In order to properly limit the process you desire, be sure you choose the one that consumes bandwidth while navigating trough websites / listening to videos in the browser.<br />


Please '''REMEMBER''' that in order to return to the normal interned bandwidth speed, you will always need to reset all the limitations from the "refresh" like button from the software toolbar after testing, otherwise the limitation will remain always ON.
Please '''REMEMBER''' that in order to return to the normal internet bandwidth speed, you will always need to reset all the limitations from the "refresh" like button from the software toolbar after testing, otherwise the limitation will remain always ON.


|}
|}
RaresB
128

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1134093"

Navigation menu