128
edits
QA/Bug Triage Guidelines: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 128: | Line 128: | ||
What you can do is to download the installer form "http://archive.mozilla.org" and have an archive manager program like "7zip" installed (freeware program). Open the folder where the installer was downloaded and right click it in order to use 7zip program to extract the installer. After doing that, you will have a folder where the Firefox build is extracted and from where you can start the actual version without installing it. As a suggestion use the command window to open it with a different profile and with no remote setting. | What you can do is to download the installer form "http://archive.mozilla.org" and have an archive manager program like "7zip" installed (freeware program). Open the folder where the installer was downloaded and right click it in order to use 7zip program to extract the installer. After doing that, you will have a folder where the Firefox build is extracted and from where you can start the actual version without installing it. As a suggestion use the command window to open it with a different profile and with no remote setting. | ||
|- | |- | ||
| Mac OS Update Privileges || When choosing to update a software on Mac OS platform, the behavior is different than on other OSes. It will prompt the current user for the credentials of the user that installed the software. So, if the administrator installed the software, and the software is available also on a 2nd user desktop, updating the software should and will request the administrators password in order to update it. If the software that you are trying to update was installed by the current user on which you are logged in, it will require the current user credentials in order to update it. | | Mac OS Update Privileges || When choosing to update a software on Mac OS platform, the behavior is different than on other OSes. | ||
It will prompt the current user for the credentials of the user that installed the software. So, if the administrator installed the software, and the software is available also on a 2nd user desktop, updating the software should and will request the administrators password in order to update it. If the software that you are trying to update was installed by the current user on which you are logged in, it will require the current user credentials in order to update it. | |||
|- | |- | ||
| Using Mozzregression Tool on Mac OS || When you need to find the regression build when an issue was introduced, 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: | | Using Mozzregression Tool on Mac OS || When you need to find the regression build when an issue was introduced, 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: | |||
• Mac OS X (10.11 only, for older versions see next bullet) | • Mac OS X (10.11 only, for older versions see next bullet) | ||
| Line 139: | Line 145: | ||
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. | 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 /> | ||
2. After credentials are confirmed it's time to install the Python 2.7 component by entering the next command "sudo easy_install pip". | 2. After credentials are confirmed it's time to install the Python 2.7 component by entering the next command "sudo easy_install pip".<br /> | ||
3. Next you will need to install the virtual environment using the next command "sudo pip install virtualenv". | 3. Next you will need to install the virtual environment using the next command "sudo pip install virtualenv".<br /> | ||
4. After the virtual environment was installed, you will need to provide a directory name for the virtual environment using "virtualenv <directory_name>" command (eg: "virtualenv mozregression" will create the environment folder under your current profile). | 4. After the virtual environment was installed, you will need to provide a directory name for the virtual <br />environment using "virtualenv <directory_name>" command (eg: "virtualenv mozregression" will create the environment folder under your current profile).<br /> | ||
5. Next you will need to activate the environment from a file that was created in the environment folder using "source /Users/profile_name/folder_name/bin/activate" command (eg: "source /Users/pauloiegas/mozregression/bin/activate"). | 5. Next you will need to activate the environment from a file that was created in the environment folder using "source /Users/profile_name/folder_name/bin/activate" command (eg: "source /Users/pauloiegas/mozregression/bin/activate").<br /> | ||
6. You will notice that your command line is now changed into "(mozregression) <code>". Now you will need to install the mozregression tool into the virtual environment using "pip install mozregression" command. | 6. You will notice that your command line is now changed into "(mozregression) <code>". Now you will need to install the mozregression tool into the virtual environment using "pip install mozregression" command.<br /> | ||
7. After the installation is completed, you can check if everything is ok using a simple command like "mozregression -h" to see if the tool help is displayed (if not you did something wrong along the way). | 7. After the installation is completed, you can check if everything is ok using a simple command like "mozregression -h" to see if the tool help is displayed (if not you did something wrong along the way).<br /> | ||
8. 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. | 8. 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 /> | ||
9. 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. | 9. 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 /> | ||
10. You will need to deactivate the virtual environment after you complete the regression using ""deactivate" command that will return you to the normal command line. | 10. You will need to deactivate the virtual environment after you complete the regression using ""deactivate" command that will return you to the normal command line.<br /> | ||
11. REMEMBER ! The environment must be activated each time when you want to use the Mozregression tool. | 11. REMEMBER ! The environment must be activated each time when you want to use the Mozregression tool.<br /> | ||
• Mac OS X (10.10 and under) | • Mac OS X (10.10 and under) | ||
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. | 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 /> | ||
2. After credentials are confirmed it's time to install the Python 2.7 component by entering the next command "sudo easy_install pip". | 2. After credentials are confirmed it's time to install the Python 2.7 component by entering the next command "sudo easy_install pip".<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" | 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. | 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. | 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 /> | ||
If | 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 | 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. | ||
| Line 167: | Line 173: | ||
| 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 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: | ||
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. | 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 /> | ||
2. After credentials are confirmed it's time to install the Python 2.7 component by entering the next command "sudo easy_install pip". | 2. After credentials are confirmed it's time to install the Python 2.7 component by entering the next command "sudo easy_install pip".<br /> | ||
3. Next you will need to install the virtual environment using the next command "sudo pip install virtualenv". | 3. Next you will need to install the virtual environment using the next command "sudo pip install virtualenv".<br /> | ||
4. After the virtual environment was installed, you will need to provide a directory name for the virtual environment using "virtualenv <directory_name>" command (eg: "virtualenv mozregression" will create the environment folder under your current profile). | 4. After the virtual environment was installed, you will need to provide a directory name for the virtual environment using "virtualenv <directory_name>" command (eg: "virtualenv mozregression" will create the environment folder under your current profile).<br /> | ||
5. Next you will need to activate the environment from a file that was created in the environment folder using "source /Users/profile_name/folder_name/bin/activate" command (eg: "source /Users/pauloiegas/mozregression/bin/activate"). | 5. Next you will need to activate the environment from a file that was created in the environment folder using "source /Users/profile_name/folder_name/bin/activate" command (eg: "source /Users/pauloiegas/mozregression/bin/activate").<br /> | ||
6. You will notice that your command line is now changed into "(mozregression) <code>". Now you will need to install the mozregression tool into the virtual environment using "pip install mozregression" command. | 6. You will notice that your command line is now changed into "(mozregression) <code>". Now you will need to install the mozregression tool into the virtual environment using "pip install mozregression" command.<br /> | ||
7. After the installation is completed, you can check if everything is ok using a simple command like "mozregression -h" to see if the tool help is displayed (if not you did something wrong along the way). | 7. After the installation is completed, you can check if everything is ok using a simple command like "mozregression -h" to see if the tool help is displayed (if not you did something wrong along the way).<br /> | ||
8. You will need to deactivate the virtual environment after you complete the regression using ""deactivate" command that will return you to the normal command line. | 8. You will need to deactivate the virtual environment after you complete the regression using ""deactivate" command that will return you to the normal command line.<br /> | ||
9. REMEMBER ! The environment must be activated each time when you want to use the Mozregression tool. | 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 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. | ||
1. First, you will need to download and install Python 2.7 from ActiveState website (http://www.activestate.com/activepython/downloads). | 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". | 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. | 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. | 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 /> | ||
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 informations also at this link -> http://mozilla.github.io/mozregression/quickstart.html. | ||
| Line 190: | Line 196: | ||
| 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 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. | ||
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. | 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 /> | ||
2. After credentials are confirmed it's time to install the Python 2.7 component by entering the next command "sudo apt-get install python-pip". You will be asked if you are sure you want to install it and you must confirm by entering "y" key and confirm the choice after. | 2. After credentials are confirmed it's time to install the Python 2.7 component by entering the next command "sudo apt-get install python-pip". You will be asked if you are sure you want to install it and you must confirm by entering "y" key and confirm the choice after.<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" | 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. | 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. | 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 /> | ||
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 informations also at this link -> http://mozilla.github.io/mozregression/quickstart.html. | ||
| Line 204: | Line 210: | ||
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. | ||
In Windows you just need to navigate to the extracted folder, hold Shift + right click on free area of the window, then click the "Open command window here" option. After the cmd is opened, write "firefox -no-remote -p" and hit "Enter" key. This will open a separate instance of Firefox with the profiler window, where you can choose to use a no update profile created before (will not update an older version of FF). After that, just test the build and see if it's reproducible. | In Windows you just need to navigate to the extracted folder, hold Shift + right click on free area of the window, then click the "Open command window here" option. After the cmd is opened, write "firefox -no-remote -p" and hit "Enter" key. This will open a separate instance of Firefox with the profiler window, where you can choose to use a no update profile created before (will not update an older version of FF). After that, just test the build and see if it's reproducible. | ||
On Mac OS, you can install the build, and in order to open it with a no update profile, you need to navigate ti instalation directory manually from terminal window (/Applications/FirefoxNightly.app/Contents/MacOS/firefox -no-remote- -p) | On Mac OS, you can install the build, and in order to open it with a no update profile, you need to navigate ti instalation directory manually from terminal window (/Applications/FirefoxNightly.app/Contents/MacOS/firefox -no-remote- -p)<br /> | ||
2. After you find a bad build, the next step would be to open a command window and start using mozregression by typing "mozregression --bad year-month-day --good year-month-day --find-fix". You need to be sure that bad build is older than good build, otherwise this won't work.Usually the good build would be the latest Nightly so use that date, otherwise it's a regression issue that needs to be treated like in previous lessons. | 2. After you find a bad build, the next step would be to open a command window and start using mozregression by typing "mozregression --bad year-month-day --good year-month-day --find-fix". You need to be sure that bad build is older than good build, otherwise this won't work.Usually the good build would be the latest Nightly so use that date, otherwise it's a regression issue that needs to be treated like in previous lessons. | ||
| Line 213: | Line 219: | ||
Windows: | Windows: | ||
1. First you'll need to have a good build date and a bad build date as for any other regression window checked. | 1. First you'll need to have a good build date and a bad build date as for any other regression window checked.<br /> | ||
2. Open a Command Prompt window and observe the path displayed. It should be something like "C:\Users\profile_name>" | 2. Open a Command Prompt window and observe the path displayed. It should be something like "C:\Users\profile_name>"<br /> | ||
3. Start Firefox with the profiler and create a test profile if you don't have one (you will need a specific name in order to find it faster). | 3. Start Firefox with the profiler and create a test profile if you don't have one (you will need a specific name in order to find it faster).<br /> | ||
4. Open "My Computer" and navigate to your OS partition in Users\<your_profile_name>\AppData\Roaming\Mozilla\Firefox\Profiles\<created_profile_name>\ folder. Remember that "AppData" folder is only displayed when "Show hidden files" option is checked. | 4. Open "My Computer" and navigate to your OS partition in Users\<your_profile_name>\AppData\Roaming\Mozilla\Firefox\Profiles\<created_profile_name>\ folder. Remember that "AppData" folder is only displayed when "Show hidden files" option is checked.<br /> | ||
5. Click the window address bar in order to view the complete path and copy it from the end to start, leaving behind only the already existing path from command prompt. | 5. Click the window address bar in order to view the complete path and copy it from the end to start, leaving behind only the already existing path from command prompt.<br /> | ||
6. With the good and bad build dates, write a command like "mozregression --good year-month-day --bad year-month-day --profile \AppData\Roaming\Mozilla\Firefox\Profiles\<created_profile_name>\" (eg: C:\Users\paul.oiegas>mozregression --bad 2015-06-06 --good 2016-02-23 --profile \AppData\Roaming\Mozilla\Firefox\Profiles\w9gzt0rd.testrelease2). | 6. With the good and bad build dates, write a command like "mozregression --good year-month-day --bad year-month-day --profile \AppData\Roaming\Mozilla\Firefox\Profiles\<created_profile_name>\" (eg: C:\Users\paul.oiegas>mozregression --bad 2015-06-06 --good 2016-02-23 --profile \AppData\Roaming\Mozilla\Firefox\Profiles\w9gzt0rd.testrelease2). <br /> | ||
Mac OS X: | Mac OS X: | ||
| Line 236: | Line 242: | ||
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 | ||
Windows - http://dl.google.com/android/installer_r24.4.1-windows.exe | Windows - http://dl.google.com/android/installer_r24.4.1-windows.exe | ||
Android studio contains also the SDK needed for this to work, but it's also a coding and debugging software for android with a friendly user interface. But if you don't need this, you can install just the command line tools. | Android studio contains also the SDK needed for this to work, but it's also a coding and debugging software for android with a friendly user interface. But if you don't need this, you can install just the command line tools.<br /> | ||
2. Install the latest Java JDK from Oracle website (http://goo.gl/rknzzs). It should be straight forward, no extra settings needed. | 2. Install the latest Java JDK from Oracle website (http://goo.gl/rknzzs). It should be straight forward, no extra settings needed.<br /> | ||
3. For best results install PDA Net software in order to have most of the Android devices drivers installed (http://pdanet.co/). However, there are cases when this software does not contains the drivers for all the new devices. For example there have been reported that LG G4 driver is not contained. In this case you will have to manually search and install the driver for your device. | 3. For best results install PDA Net software in order to have most of the Android devices drivers installed (http://pdanet.co/). However, there are cases when this software does not contains the drivers for all the new devices. For example there have been reported that LG G4 driver is not contained. In this case you will have to manually search and install the driver for your device.<br /> | ||
4. Next step is a bit trickier and you must pay attention at what changes you are doing. | 4. Next step is a bit trickier and you must pay attention at what changes you are doing. | ||
| Line 246: | Line 252: | ||
- Chose the "Advanced System Settings" option from left side of the window, and from the bottom of the displayed window select "Environment Variables" option. | - Chose the "Advanced System Settings" option from left side of the window, and from the bottom of the displayed window select "Environment Variables" option. | ||
- In the "Environment Variables" window, you need to add first a new "System variable". Click the "New..." button and add "ANDROID" for variable name and in the variable value field, you need to add the path where you have installed the SDK (eg: C:\Users\profile_name\AppData\Local\Android\sdk where "profile_name" is usually your PC user name). After that click "Ok" button to save the variable. | - In the "Environment Variables" window, you need to add first a new "System variable". Click the "New..." button and add "ANDROID" for variable name and in the variable value field, you need to add the path where you have installed the SDK (eg: C:\Users\profile_name\AppData\Local\Android\sdk where "profile_name" is usually your PC user name). After that click "Ok" button to save the variable. | ||
- 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. | - 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). | 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. | 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 /> | ||
7. After this, you are almost good to go. Connect your Android device to the PC, run a command window (make sure you have the latest mozregression version "pip install -U mozregression") or the Mozregression GUI. | 7. After this, you are almost good to go. Connect your Android device to the PC, run a command window (make sure you have the latest mozregression version "pip install -U mozregression") or the Mozregression GUI. | ||
For the command window mode, the only thing that is different from the PC testing is the "--app=fennec" command that you need to introduce before good & bad dates. The command will look like "mozregression --app=fennec --good 2015-05-06 --bad 2015-07-09". | For the command window mode, the only thing that is different from the PC testing is the "--app=fennec" command that you need to introduce before good & bad dates. The command will look like "mozregression --app=fennec --good 2015-05-06 --bad 2015-07-09".<br /> | ||
Notes and Tips & Tricks: | Notes and Tips & Tricks: | ||
| Line 286: | Line 292: | ||
| How to deal with bugs that are reproducible between the latest official release and the latest Nightly || One of the possibilities when working on the Bug triage task is to encounter bugs that are reproducible between the latest official release and the latest Nightly (for example, the bug is reproducible only on the latest Aurora). In this case we take the following actions: | | How to deal with bugs that are reproducible between the latest official release and the latest Nightly || One of the possibilities when working on the Bug triage task is to encounter bugs that are reproducible between the latest official release and the latest Nightly (for example, the bug is reproducible only on the latest Aurora). In this case we take the following actions: | ||
1. Confirm the bug | 1. Confirm the bug<br /> | ||
2. If it's the case: set the right component | 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) | 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) | 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 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. | ||
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: | ||
1. First you will need to navigate to https://developer.apple.com/downloads/ and if you don't have an apple ID, you should create one. | 1. First you will need to navigate to https://developer.apple.com/downloads/ and if you don't have an apple ID, you should create one.<br /> | ||
2. After you manage to Sign In, a list with available downloads for Apple Developers is displayed. You need to chose the most recent "Hardware IO Tools for Xcode" package (you don't need Xcode installed to use this tools). Expand the package from "+" sign on the left and click the link from right side with ".dmg" format. | 2. After you manage to Sign In, a list with available downloads for Apple Developers is displayed. You need to chose the most recent "Hardware IO Tools for Xcode" package (you don't need Xcode installed to use this tools). Expand the package from "+" sign on the left and click the link from right side with ".dmg" format.<br /> | ||
3. After the package is downloaded, mount it from downloads. A folder will be opened after containing the tools from the package. You will need to double click the "Network Link Conditioner.prefPane" file and choose to install it when prompted. The tool will be installed and added to "System Preferences" panel and you can always start it from there, each time when you need it. | 3. After the package is downloaded, mount it from downloads. A folder will be opened after containing the tools from the package. You will need to double click the "Network Link Conditioner.prefPane" file and choose to install it when prompted. The tool will be installed and added to "System Preferences" panel and you can always start it from there, each time when you need it. v | ||
4. The Tool comes with a couple of predefined profiles, but I suggest you to create a new one. You can do this by tapping the "manage Profiles" button. If grayed out, you need to unlock the edit possibility by clicking the "Lock" icon from bottom left and enter the user and password. | 4. The Tool comes with a couple of predefined profiles, but I suggest you to create a new one. You can do this by tapping the "manage Profiles" button. If grayed out, you need to unlock the edit possibility by clicking the "Lock" icon from bottom left and enter the user and password.<br /> | ||
5. A new window will pop up where you can click the "+" button from bottom left to add a new profile (any name you desire). | 5. A new window will pop up where you can click the "+" button from bottom left to add a new profile (any name you desire). <br /> | ||
6. After you have a new profile created, you will need to enter the desired values in "Downlink Bandwidth" for download speed and in "Uplink Bandwidth" for upload speed. Please take into consideration that the speed there is represented by default in "Kbps" which means that if you want to simulate a real 100KBps download speed, you will need to multiply the value with 8 to have the value in "kbps" (800kbps). | 6. After you have a new profile created, you will need to enter the desired values in "Downlink Bandwidth" for download speed and in "Uplink Bandwidth" for upload speed. Please take into consideration that the speed there is represented by default in "Kbps" which means that if you want to simulate a real 100KBps download speed, you will need to multiply the value with 8 to have the value in "kbps" (800kbps).<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. | 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 interned bandwidth speed, you will always need to switch the Tool to "OFF" after testing, otherwise the limitation will remain always ON. | ||
| Line 307: | Line 313: | ||
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: | ||
1. First you will need to to navigate to https://netbalancer.com/download page and download the latest version of the NetBalancer software. The unregistered version is limited to a maximum of 3 process priorities/limits and 3 rules at a time. | 1. First you will need to to navigate to https://netbalancer.com/download page and download the latest version of the NetBalancer software. The unregistered version is limited to a maximum of 3 process priorities/limits and 3 rules at a time. <br /> | ||
2. Install the software and restart the computer after. | 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. | 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. | 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 /> | ||
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. | 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 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. | ||
|} | |} | ||