QA/Platform/Graphics/Guides: Difference between revisions

QA/Platform/Graphics/Guides (view source)

Revision as of 16:03, 7 May 2015

934 bytes added , 7 May 2015

→‎Using Mozregression

Ashughes

Confirmed users

14,525

edits

@@ Line 16: / Line 16: @@
 '''''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.
-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.
+) 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 at all (eg. if it crashes)
+) 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.
+) 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 ==