QA/Platform/Graphics/Guides: Difference between revisions

← Older edit

QA/Platform/Graphics/Guides (view source)

Revision as of 19:34, 3 December 2015

539 bytes added , 3 December 2015

→‎Finding a Regression Window

Ashughes

Confirmed users

14,525

edits

@@ Line 1: / Line 1: @@
 = Finding a Regression Window =
-== Installing Mozregression ==
-Instructions for Windows:
-* Download and install [http://www.activestate.com/activepython/downloads Python 2.7]
-* Open a Windows command window (Run cmd.exe)
-* Execute this command: <pre>pip install -U mozregression</pre>
-* Confirm mozregression is installed by executing this command: <pre>mozregression --version</pre>
-* If you get stuck, see the full instructions [http://mozilla.github.io/mozregression/install.html here]
 == How Mozregression Works ==
-Mozregression works by downloading Firefox Nightly builds from a range of dates allowing you to easily narrow down the first Nightly which introduced a bug. Once a Nightly is downloaded and installed, Mozregression will start Firefox with a temporary profile and allow you to test your bug. After testing the bug, you give Mozregression a ''good'' or ''bad'' command and it will split the range in half, downloading the next build. Once the range has been narrowed down to a single day it will give you a pushlog for the build that will identify the changes which may have caused the bug. This should be attached to the bug report.
+[http://mozilla.github.io/mozregression/install.html Mozregression] works by downloading Firefox Nightly builds from a range of dates allowing you to easily narrow down the first Nightly which introduced a bug. Once a Nightly is downloaded and installed, Mozregression will start Firefox with a temporary profile and allow you to test your bug. After testing the bug, you give Mozregression a ''good'' or ''bad'' command and it will split the range in half, downloading the next build. Once the range has been narrowed down to a single day it will give you a pushlog for the build that will identify the changes which may have caused the bug. This should be attached to the bug report.
 As mentioned above, the range will first be narrowed down to a particular Nightly build, then continue to an Inbound build, which will often get us down to a single patch.  After the Nightly build search is done, mozregression will note the range for it, then continue to bisect the Inbound builds.  When recording the results of mozregression, it is useful to record the Nightly range as well, even if the Inbound range is found.
@@ Line 16: / Line 8: @@
 '''''Note: We recommend [[#Narrowing_the_Range|narrowing down the range]] manually before using mozregression.'''''
-If you don't know the dates, simply run ''mozregression'' from a terminal/command window. This will download Firefox Nightly builds starting from January 1, 2009. However, you can save yourself some time and hassle if you give mozregression a narrower range. You may find some of the really old builds will just fail to work, especially on newer platform versions.
+Using mozregression is as simple as running ''mozregression'' from a command prompt. However, this will start with Nightly builds from January 1, 2009 which could make finding the regression range a longer process. Assuming you know the build dates for the first bad and last good Nightly you would run ''mozgression --good YYYY-MM-DD --bad YYYY-MM-DD'' where YYYY-MM-DD is the date of each build. See [[#Narrowing_the_Range|narrowing down the range]] for information on getting those dates.
+) Open a command prompt and run ''mozgression --good YYYY-MM-DD --bad YYYY-MM-DD'' where YYYY-MM-DD is the range of dates you want to test.
+) Mozregression will download builds between those dates, start with a new profile, and allow you to test for your bug.
+) Once you're done testing, switch back to the command prompt and mark the status of the build:
+* ''bad'' if the build reproduces the bug
+* ''good'' if the build does not reproduce the bug
+* ''skip'' if you want to skip testing the bug in that build
+* ''broken'' if the build does not work and you're unable to test your bug
+) Mozregression will bisect the range and grab the next nightly, repeating the process above
+) Once the range has been narrowed to a single day it will provide changeset IDs and a pushlog for the range.
+* Make note of this and copy it to your bug report.
-If you know the dates, simply run ''mozgression --good YYYY-MM-DD --bad YYYY-MM-DD'' where good is the date of the last build you know is good and bad is the date of the first build you know is bad.
+) Mozregression will then begin bisecting the range with mozilla-inbound builds
+* You can skip this step unless someone has asked you to bisect the range further.
 == Narrowing the Range ==